Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
RPC server migration - timestamp issue with legacy Textpatterns
Over the past months, the Textpattern website infrastructure has been audited and is moving to a new home. There has been considerable consolidation and minimal downtime as we work through each website, bring it up-to-date and onto a more sustainable server. The full story is being told here if you’re interested.
The vast majority of issues that we’ve discovered have been resolved or worked around, thanks to hard work and skills of Stef, Oleg, Jools and Phil. There is one known issue that we cannot reasonably mitigate against, and you should be aware of it in case it appears. This will be relevant from Sunday, October 14th 2018 when I plan to migrate the RPC server from the old server to the new one.
Curious? Choose your adventure:
If you have Textpattern 4.6. or earlier*, it uses RPC to check for translation and language pack updates. The language panel may show there is an update available for your language; after selecting the option to update the language, it may still say there is an update available, when in fact there isn’t.
Both update notices can be ignored and the language strings are updated properly. It’s a recently discovered bug. Nothing about your Textpattern site has gone wonky, you have done nothing wrong. No other Textpattern functionality is affected by this bug. Accept it’s a bug, go about your business, have a good day.
If you have Textpatttern 4.7.0 or later, you are not affected by this issue. Textpattern 4.7.0 and later does not use RPC for language or translation updates, they are included locally. Go about your business, have a good day.
The issue arises from timezone differences between the RPC server and the Textpattern instance checking for updates. If you’re in the same timezone as the server (UTC), you should be OK and RPC will continue to work. If you’re in another timezone, you may encounter this issue.
Jools has modernised the RPC server codebase to maintain compatibility with both legacy Textpattern installations around the world, and the current technologies we have on the new servers. We have a more maintainable solution for the future.
The RPC server exists to serve legacy clients, including language translations and the pophelp feature. Pophelp will continue to work as expected, and is not affected by this bug.
Questions? Please leave a reply below.
Thank you for reading.
Last edited by gaekwad (2018-10-11 21:29:57)
Offline
Re: RPC server migration - timestamp issue with legacy Textpatterns
gaekwad wrote #314550:
If you have Textpattern 4.6. or earlier*, it uses RPC to check for translation and language pack updates. The language panel may show there is an update available for your language; after selecting the option to update the language, it may still say there is an update available, when in fact there isn’t.
If you experience this issue, please check in the Diagnostics whether your PHP and MySQL server times are identical. They sometimes mismatch on local *AMP servers, mines are
Server local time: 2018-10-12 08:28:49
...
Database server time: 2018-10-12 10:28:49Please let us know if it’s not the case to help debugging, thanks.
Offline