Marc

We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you.

No, you wouldnt have to do anything on your end. It submits to google and bing

Please check your conf_global.php file, and ensure if you are using https on the server, you also have your address set to https there. If thats not the cause, please update your access details on file for the new server, and we can get this looked into

Ah, the issue there is the htaccess you have in place. You would need to ensure any connections to the following location are whitelisted from any IP or password authentication /index.php?app=core&module=system&controller=marketplace

It is indeed. This requires functions only available on the cloud platform

No problem at all. Glad to hear you have that sorted

You would upload a fresh set of files from your client area. Once you have done this, you will see blog available to install from System>Site Features>Applications 🙂

Anything we create would be added to the core product, as a core item. We would not create 3rd party items. I'm not sure where you get the harassment from there. It really is as simple as needing you to disable 3rd party items to test things. We're not harassing you for not doing so. This is entirely up to yourself.

Thank you for coming back to let us know, and very glad to hear you found the issue 🙂

I would need an example of this in order to take a look at the problem.

Could you please confirm where you have the installation? That would not work on a local install

Im not sure what would be causing that issue, as its clearly accessible. I would ask however, why you would be doing this? Are you aware it submits itself?

I wouldn't say that is the case, and sorry to hear you feel that way. I believe the correct analogy you were looking for is you believe that they are treated like covid. This isn't really the case, unless they cause symptoms like it. To explain the above. We find that most issues in support are caused by 3rd party items and badly configured environments. So naturally, you eliminate those 2 items before anything else, which is why it appears that way. But to do otherwise would be like admitting a patient to hospital with chest issues, who is struggling to breathe, and not testing to see if they have covid first. So your analogy in that context actually fits better than perhaps you intended. Its not something against the authors, its simply logical steps. If we updated the editor and upload process, and there was an editor issue related to uploads, we would look at that first, as logic dictates that is likely where the issue is. Its nothing more than this.

Before we go on to this, did you find the actual issue there? I ask, as it doesnt sound like the cause was found. If not, its very very likely, even if we could find a way for you to do this, it will fail

There isn't really a workaround there. It's an addition. There are performance reasons we don't add this to the core platform, as mentioned in the topic above. While there may be sites who can use things like this, they are not necessarily always something that is good to add to the core platform. If this was the case, the marketplace wouldn't exist. This is where the 3rd party community comes in. Application and plugin developers develop for people who purchase their application or plugin. So by definition, in this case, the only people purchasing that addon are the people who need that added. We do the same, but have a broader audience. The people who are buying our product, are not only people who need that feature added. There is nothing wrong with that. Its just the way it is. I'm sure there is a store somewhere that sells leopard print car seat covers for Ferraris. I'm also pretty sure thats never going to come as a default option

Please feel free to post that up within our suggestions area.

Ah, only in feeds. No, you would indeed need a plugin for that.

Please could you let us know what you found to be the cause? Others may find the same issue, and its always handy if people know when they search the community

It was indeed memory limit. Not sure why it wasnt being respected on your server, but it was certainly the issue, as the server was literally stating it hit the limit there. As a suggestion for any future items like this. If it's a large scale item such as moving items, changing servers, changing your domain etc, always backup everything fully before you start, and only ever do one at a time. Doing it in the manner you describe above will very likely cause you issues. 🙂

I would need to know the name of the member in order to be able to take a look at this

We would need an example member who you believe should be showing. We can then take a look from there

You can then add this to your menu if you wanted to do so, in the manner described here https://invisioncommunity.com/4guides/global-settings/setting-up-your-menu-r27/

I must admit I'm not sure as to what you mean here. If you can point out the plugin, we can then advise accordingly. I think that would be the best way

I have created a ticket for you on this, so we can look into the issue further

Glad to hear you got the issue sorted 🙂