Pierre Mobian

I think you’re putting forward the need to use a developement environment AND a staging environment, distinct from your production site. This has become much more affordable as hosting costs have gone down. It also implies strict work methods, such as versionning (SVN, Git) and publishing methods and processes beyond the scope of that question, but worth learning – in fact they should be a requirement for any developer worth his salt – pun intended.

Also note that all plugins put forward whether they are compatible with the Wp version you wish to upgrade to – you can find this in your dashboard and on the repo, and most developers update their plugin infos for a major WP new version, so keep an eye on this.

The extent of what you wish to test is then entirely up to you. Do you simply wish to make sure there is no blank page or 500 error in the site after the upgrade, or need to check every single pixel is properly aligned under every browser and screen size ? Then again there are solutions for each situation, but they imply time and cost to logically determine depending on your project – a personal blog and a multinational company site do not have the same implications.

Failing to deploy such a very elaborate, more costly, but strict and fail-proof solution, you could choose a more basic solution, such as a staging environment with a cloned version of your site (which you maintain similar to your official/live site, there are sync plugins for that) on which you do the upgrade, and on which you then conduct basic tests with a crawler to make sure there are no empty, broken pages, 500 errors etc, – after which if things go well you do the same on your live site.

That question is very relevant and would require more explanations. Your mileage may vary…

• This reply was modified 7 years, 3 months ago by Pierre Mobian.
• This reply was modified 7 years, 3 months ago by Pierre Mobian.

Do you have access to your site error log, by Cpanel or Plesk for example ? Else ask your hosting provider, as such logs may directly provide the error causing this.

Hello

Updates based on an already hacked site will not fix the issue.
Did you properly reinstall your site by deleting all contents in your hosting space, and then uploading a fresh, up-to-date WordPress ?
Are all your plugins and your theme Enigma also up to date ? Is your hosting environment (Apache or NGnix server, MySQL database, PHP version ?) also up to date and secure ? Did you change all your access codes including FTP and SSH access on your local PC ?

Which antimalware tools did you use ?

• This reply was modified 7 years, 3 months ago by Pierre Mobian.

Hi,

I don’t believe WP uses any fancy protocol or port for its updates, usually fetched on official servers hence on an HTTPS address / 443 port. Updates may be caused by a number of things, of which I recently saw happened to be an over quota hosting space.
*After creating a backup*, you may opt to download the latest WP core from the official site on your machine, and upload it to your hosting space. *Reminder: Backup first* your files and database.

Hi,

Did you properly reinstall your site by uploading a fresh, up-to-date WordPress ?
Are all your plugins and your theme Enigma also up to date ? Is your hosting environment also up to date and secure ? Did you change all your access codes ?
Failing to follow all those steps or simply reinstalling your site based on the backup of a non-secure site may lead to a still unsecure site, and what you describe seems like a vulnerable site hackers will keep hacking…
Good luck.

Hi,
There are indeed ways to debug a cronjob. What kind of hosting are you using ?
What do you call “does not seem to be working” and “did not help” ? Do you see any message and which one ?

If you have a hosting space under tools such as CPanel or Plesk, you’ll have direct access to error and access logs. Error logs could underline an issue with the cronjob, and logs will confirm whether the cronjob indeed runs as planned.
Under Linux and on a default installation the cron jobs get logged in
/var/log/syslog.

Your hosting provider may also help you with this.

On which kind of server is your site hosted ? You may have a load issue on the server side, either created by an entirely different sites sharing your hosting server, or your own site. Logs from the hosting provider may shed some light.

Not liking such characters is not restricted to WordPress, and for good reasons. In order to properly use them, and as importantly enable both human and SEO bots visitors to read your images, I’d advice to rename such images with proper naming (no space, no special chars) – you could for example turn them into green-sofa-250-pounds.jpg. Many free images utils can do that, or you can also rename batches of images in command line if you have a server access.

Good luck.

This may be due to a variety of causes ranging from hardware failure to hack consequences.
The safest way to restore your site is to use the backup which hopefully you create on a regular basis. Failing that, and noting you’d be better off starting after that incident if it was not part of your routines, I’d contact the hosting provider as they sometimes/often do backups on their end for a length of time that remains to be determined – YMMV.

Good luck,

• This reply was modified 8 years, 2 months ago by Pierre Mobian.

Hi,

What kind of contents / URLs does this apply to ? Care to share a screenshot ?

Interested in such an option too, however I guess the developer is busy elsewhere as no merge followed up the notice dating back from May – in which he said he’d been busy but would come back soon to take care of merges and plugin continuation ?
Thanks.

Hello to all,

Has anybody ever worked on a French version ? Interested in sharing ?
Is there a place where the plugin can share its existing localizations/translations ?
Else I’ll consider doing it but might as well not reinvent the wheel ??
Have a nice day.

Hello
Apparently not properly set, not sure how this was overlooked, thanks.

Thank, I also found relevant plugins in the meantime and will explore those options.

As it seems you used PHPMyAdmin or an equivalent, what was the output or error message from your mysql query ?
Do you have a hosting account console, and are all the limits in there ok – no over-quota alert ?