Luuuk

As far as I understand, when you supply the Uploads folder to IPS for the Self hosted -> Cloud conversion anything custom inside the Uploads folder would be lost. I can eventually manage moving ancient images to an external hosting service and update massively my database to point there. What bothers be is a custom SVG folder (my site/uploads/SVG) holding recent SVGs because they can't be attached (for a reference my old topic) . I guess nothing changed in IPS 5 and attachments still would disallow SVGs, right?

Hi, I am self-hosted and I have a very old folder (dated back to 2010) with images (not attached but linked directly in thousands of posts): My site/custom (also lots of subfolders) I would like to consolidate items + make easier my file system backups and move the whole folder here: My site/uploads/custom (including all subfolders) (then I also could update en masse links in the database to point to the new location) My questions are: 1. Is it safe to place the custom folder there in the meaning: your software won't alter/delete it as not belonging to the software? Any "disallowed" names? 2. Will the custom folder be preserved "as it is" after deciding to upgrade to the Cloud solution? I know that after upgrading no access to the file system at all but will the already posted links pointing the custom location still work in posts?

I believe the text refers either to: - Marketplace removal and Plugins deprecation are not related to each other. [My comment: and I did not relate them, I just provided two separated infos for the OP] - All developers previously providing/distributing plugins for IPS 4.x must to convert the plugins to applications to make them work with IPS 5.x.

Hi, 1. Invision Marketplace is ditched for good so yes. Also, Plugins are deprecated in 5.x: 2. There is a community attempt to provide a basic listing similar to the old Marketplace: Invisioneer Marketplace Directory Some developers already introduced "Compatibility with 5.0 Beta".

Discussed here:

I have to agree. Those replacements can even totally change a meaning and while the link could be "easier to remember" but for wrong reasons. Let me use the following extreme example from Polish language: "łaska" vs "laska" They are actually two different words and each of them have multiple meanings and none of them cross each other. - The first one could be: "would you be so kind...", "grace", "pity", etc. - The second one could be: "walking stick" but in a slang also a "hot girl" or "blowjob" 😆. Imagine the word placed in an unfortunate combination and you'll get a link sounding like a p*rn. Jokes aside, such problem could be in different languages too so you can't guarantee what actually you render as a "message" in the link...

For now the only option is a free plugin:

The permission for creating a new topic covers moving posts as well. Look from this perspective: moving some posts to an existing topic does create a "new topic" in the meaning that you add more data to the existing topic. So as pointed out make sure to enable permissions for your group in the destination forum:

Expand your ACP user menu > Theme:

Like I said, you don't need to upgrade to get around the issue. Just remember to close the IPS message (every time it is re-appearing) and reload the page. That's all.

Exactly. Regardless of the bug you can still access the stuff if you close the message and reloaded the page ... until the next "important" message. You said that you are on 4.7.2. The fix is in 4.7.8.

I think that was the issue: You potentially either closed an IPS message on top and reloaded the page or upgraded from 4.7.2 to the later version. The fix supposes to be in 4.7.8.

In case of third party themes it is no longer possible since IPS 4.5. The limitation is related to an inaccessible ACP panel in case of outdated or badly designed themes. Now, the only option available is to swap between the light <> dark default ACP theme.

Check this out:

Oh yes. I know what exactly you are up to. As I said: "for now" = just wanted to provide a temporary "solution" until the whole page will be secured in other way. Could not provide any other way since I did not test the spiders at all.