Marc

No problem at all 🙂

Its a child theme of "default new nov" 🙂

I added this as a bug just to get some clarification for you. Paypal has a test endpoint. So we switch to the test endpoint. Stripe however doesnt. It has test keys. So you would need to switch to using test keys (we wouldnt have them. Only you would if you set them up in your stripe account) It is still added as a bug by the way, as we can check the key to see if it appears to be a test key or not.

This seems to have been being caused by cache on one of your 3rd party applications. When they were all disabled and enabled again, its corrected the problem.

There is no setting for the background of individual forums. That can only have been custom work you have there. The only custom colour for forums is the "Use a Feature Color?" setting, which can be found in each forums settings. It may be your theme is using that

I have reset that for you, but you should install in the same test location each time. Usually we advise on using a subdomain, as you can then point it wherever is needed

Once you have done your upgrade, let us know what the errors are if you have any. Its not possible for us to really say whats happened without those

We would need more information on what issue you had in order to assist with that. If you can let us know what was happening we can then guide

Glad to hear you now have the fix for the issue. Its always worth checking first. Even a friendly "Has this been fixed? Just looking and not sure it has been because...." would have saved a lot of debate for the both of us. 🙂 We really are trying to work to make things better for you, not work against you.

Thanks for the reply 🙂

You should not be deleting content from any table if you want to preserve content The issue is still open at present

Its not possible to change core links at the present time

Please could you create a new language pack, and ensure its selected in the admin CP, then check?

Actually I was incorrect. It was in version 19, so there is already a fix for it. You are behind in your updates. Its in the release notes shown here You will also note that there were several updates to the software. All within version 4

Sorry to hear you feel the need to attack developers on their progress. It has actually been fixed in .20 which is currently at beta 3. Which to add, is our next release of the software, so actually the earliest release it could have been in. In answer to your question 3 beta versions of the brand new beta 5 release, including thousands of bug fixes 3 public holidays, of which well needed time off was taken by developers 3 beta versions of .20 (of which actually include the very fix you are talking about) Complete recreation of our site to be compatible with version 5 of the platform, in preparation for the first major release in over a decade Movement of all cloud assets to a new storage system, which was quite a large undertaking Adding in of new WAF to our cloud infrastructure for better protection of our customers Your opinion wasn't the issue. Your language toward hard working staff was.