Marc

Please note that changing the URL on file will not cause what you are seeing there. Check what you have changed in your conf_global.php file first of all, and if you Would Like us to take a look, please let us know. Note, you will need to ensure you update your access details if you would like for us to take a look for you

I see your domain is now sorted, Manuel 🙂 Glad to see you are getting up and running

I see Daniel managed to get you sorted there. Please do let us know if you have any further issues 🙂

Glad to see we were able to get you back onto your site there. Please let us know if you have any further issues

I would suspect you are probably correct indeed 🙂 Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

There is no way in which to sync the 2 together. It posts a topic as you have set it, but it would not then syncronise the number of reactions from the 2 separate places

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

To clarify, what you have changed there is actually correct

If you see guides like that where its not mentioned, of course let us know. I have added a note to go through them however. Topics of course, it would depend on the author doing so

That one is a pretty simple one. You cannot edit files on cloud. If anything mentions editing files, thats not something you can do there

Thats excellent. Very glad to hear you got a solution to the problem there

Before I look further into this, are you holding URLs with an @ in moderation? If so, thats what will be causing the problem. This images by the way are the retina versions of emoticons.

You would need to check this with your server host, as if you have exif installed and its not reorienting them properly, its an issue with exif on the server.

You were missing a column in the database. As mentioned, the support area will show if there are issues and give you the opportunity to fix those 🙂

Glad to hear you got that sorted. What plugin was that, out of curiousity?

No problem at all 🙂 Thats what we're here for

As we cannot assist with the designing of pages, I have moved this to community support for you. There are quite a lot of people who have done a lot of different designs with these. So Im sure someone will have something that fits the bill

I think at this point these are actually more suggestions than anything support related here. Of course we are always looking at ways to improve the product, and if you feel inline help is something you would like to see in the product, please do post that up in the suggestions area. Suggestions are very much appreciated always.

If you cant print it from your browser, thats really a browser issue rather than anything else. If the image itself is too large, the wrong dimensions or otherwise, we have no control over that as it comes from easypost

As that was generated by an old version however, I Would recommend letting us know if you see the problem happen again naturally, rather than inserting that set of data manually. While I understand what you are saying there, clearly there is something off with that specific item

I have moved your ticket to our developer connection forum, which is better placed for your request here.

As was mentioned in the message to you originally While I appreciate your frustration, its something that wasnt really intended to be used in that manner. Essentially, its an oversight in that respect. Its related to the period lengths rather than the prices themselves. These can take some time to go through and decide on what we are going to do with them. At present this is still being gone through. As you know this is not intended to work in that manner, all I can do here is reiterrate what has already been said. A warning, while stopping others from doing the same, is not going to solve your problem here. I understand you believe there has been nothing done to address this, however the reality here is that you havent seen anything done to address it. This is a large area of the software in which cant be simply changed without internal discussion, coding, and then implementation. This can at times involve an extended period of time to address

I have just confirmed this with my colleagues. ALCs are used because some objects are purposely not public, while others are. So for the purposes of our software that is indeed what is required. I have made a note to update our documentation to include this. Previously this selection was not present when the documentation was done, which is why it is not there at the moment. Hope that clarifies

Sorry to hear you feel this was not dealt with correctly, however you were not asked to debug anything there. In fact to the contrary. We had requested access so we could take a look. With regard the AWS item not following recommendations, I will bring this up internally. Please however be aware that items will change at places out of our control, and these can take time to implement on our end. The S3 documentation has also been noted internally to be looked at. There is certainly no intention in any way to be difficult. I'm glad to see it resolved your issue in any case

Just to point out on this one, we provide guides on how to set up our side, and attempt to provide the AWS side. However you dont actually pay us to provide guides on how to set up AWS. I can certainly take a look at that, but I do need to clarify this point.