Jump to content

Nathan Explosion

Friends
  • Posts

    7,135
  • Joined

  • Days Won

    129

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Release Notes v5

Invision Community 5 Bug Tracker

Forums

Events

Store

Gallery

Everything posted by Nathan Explosion

  1. I'm not going to do any more testing of it - better things to do with my time. I've reported it...my work is done. Here are your reproduction steps, for anyone testing it... 1) upgrade to android 14 2) install the pwa (not tested existing pwa being present, no need to do so on my part) 3) open it up. 4) expect the message at that point.
  2. For reference: Android 14, November patch on Samsung (several different device models)
  3. 4 If on-premise, you likely have a credits.txt file in your site root which gives the exact version number used by your current installation.
  4. Download the ckeditor plugin's zip file and upload it using the ACP: Use caution - if you have a test instance, use it.
  5. Looks like you're wrong. There is no ordering on the select query that creates the block listing - it's at the mercy of the order in which the widgets were added to the core_widgets table, which would be the order in which applications/plugins were installed (System likely first, then order of installation of other apps)
  6. I think this means you want to have the editor hidden. If so, custom CSS: li#_report_message{ display:none; }
  7. I followed the instructions in the blurb they provide as a response to the request - and that is in this post, with links (obviously, you'll need to provide your server's IP instead):
  8. Just to add for anyone reading the above - if you go to http://www.reddit.com/oembed?format=json&url=https://www.reddit.com/r/reactjs/comments/14s3r1j/adding_the_new_threadsnet_social_share_button_to/?rdt=53260&scheme=https (this is the URL produced by Invision to connect to Reddit to get the oembed code) it will redirect to the https equivalent: https://www.reddit.com/oembed?format=json&url=https://www.reddit.com/r/reactjs/comments/14s3r1j/adding_the_new_threadsnet_social_share_button_to/?rdt=53260&scheme=https ...and produce the expected response. I am not indicating here that it's going to fix things for those currently blocked (you will need to contact Reddit to get your server IP unblocked) nor am I indicating here that the change by Invision will stop people being blocked going forward - I am only indicating that in my case above, we have not seen any further blocks since making the change after the second unblock being done.
  9. Just as a bit of information to add to the mix here... A few weeks ago I assisted someone on a problem with Reddit embeds on their own site (non-Invision) which had the same problem - Reddit unblocked their IP address, but a few days later it was blocked again. Contacted Reddit again, they unblocked it but advised us to review the embed code being used. It was then that I spotted that the URL being used for the oembed endpoint was http://www.reddit.com/oembed - updated it to https://, and we've not seen any further blocks. The endpoint for reddit in \IPS\Text\Parser is http://www.reddit.com/oembed
  10. Youre overthinking it there... EVERY field in a Pages database has a "topic format" field - make use of it:
  11. See attached - want to change the phrase? The language string is called neplugin_empty_topicfeed (NE) Empty topic feed 1.0.0.xml
  12. Or maybe just use this as the topic format for your content field... <div data-ipsTruncate data-ipsTruncate-size="3 lines" data-ipsTruncate-type="remove">{value}</div>
  13. Oh, that works in plugins/applications where you have complete control over the code of the fields. You don't have that with themes as fast as I can see.
  14. I thought so... In that video, you appear to be expecting the toggling of the field to be 'live' - but it doesn't work like that. Change the first field, scroll down, click Save and reload, check the second field. That's what I am doing in the videos.
  15. OK, as you can see in my video it's working fine for me. Attaching another video of the full thing being done. video.zip
  16. Mate...why are you still trying that? Look at what I posted...
  17. How much is it worth? mwahahahahaaaa But seriously...this is the conditional for the second of the 2 settings in that video: <?php return (boolean) $this->settings['neapp_theme_setting_1'];
  18. You mean this... Editing Default — Mozilla Firefox 2023-12-12 17-13-34.mp4
  19. In that case, the bug would be the language string being incorrect. Anyway - it's reported, up to Invision how they handle it.
  20. This reminds me of another annoying issue while you are poking around in that area - this is what someone sees if content moderation is enabled on an account after they have replied to a topic: If the content must be approved before the content can be edited then an edit link shouldn't be there, and I shouldn't be able to edit (which I can if I click the link)
  21. There we go - fleshed out a bit more... https://www.sosinvision.com.br/index.php?/file/40-profile-field-per-user-group/
  22. Before diving in to that custom app idea...might be an idea to show, in a screenshot, what you are referring to for hiding. Why? Because profile fields, which might be what you are referring to by "Personal information" can already be hidden from view:
  23. When v5 comes out, upgrade to it.
×
×
  • Create New...