Pierre Mobian

Hi,
Simply as stated: your CMS is not allowed to write to that dir, due to ownership and/or permissions errors. You can try in another new dir created by FTP or see with your host provider.

Regards.

Hello,
This looks like a time-out on the hosting side. Depending on your hosting solution I would check for error in the logs of the GUI (Cpanel, Plesk, custom) or with your hosting support. It seems strange given the volume of WordPress updates but there may be limitations on the server, in Web or PHP parameters. No other fancy setup in your site in terms of security extensions, configurations, plugins ?

Hello

The plugin complains about a missing table “postsam_wp1.wp_wpforms_tasks_meta” and therefore will not be able to install properly, hence the next MySQL error. There is no error in the WP sources, the debug is just an indication on which part could not proceed.

I guess you changed tables prefix from wp_ to postsam_wp1_ which is a good security practice
Does everything else work fine in the site ?

Hi,

This is typically caused by a PHP function included in the PHP8.0 version but changed/fixed in 8.1, if no files/dir ownership or permissions were changed in between.
If you do not specically need 8.0 you are safe to go with 8.1, however for a Production site that may be a courageous choice ??

Hello

You’ll need to provide more details in order for anybody to troubleshoot that issue.

If your issue is technical, note your server environment.

If is indeed linked to a plugin issue, server logs will provide details on what happened,for example a blank page, PHP fatal error etc.
You may get those in your hosting tool interface and/or set WP to debug mode in order to get them.

Regards.

Nothing personal against original poster who clearly was just looking for features or support, but such reviews should be deleted or at least not taken into account in the plugin note, a question made for the plugin support, to which they are known to reply efficiently and quickly, has no place here. I’d like the WP plugins notes to be a real reflection of users experiences, this does the community no favor when a competitor or poorly informed customer can downvote a plugin without any ground.

Many optimized plugins may run perfectly fine on your site, whereas just one badly coded plugin may single-handedly take down your site.
I suggest you setup a development site, cloned from your main official one, where you can test everything you need first.

Several free plugins from the plugins directory will help you measure how long pages generation takes, and of course cache plugins can bring a much better experience.

Unused / unactived themes and plugins have nothing to do in a production site anyway, if only because that’ll save you from getting update notices for things you do not use, but mainly for security reasons of course.

Have you tried a simple PHP script emailing a test message to narrow down whether this is a WordPress or PHP issue ? Do you have access to logs showing if the message was sent and not received rather than not going out, and is your domain setup OF in terms of SPF and DKIM, those configurations proving to email providers that your messages are legit when sent from that server ?

The cURL option may be blocked by an option (firewall) with your hosting provider. The cron may also be called through a relative path and not the full site address that times out for you.

Some hosts also run several PHP versions, have them check into that. If you have SSh access to your hosting space you may check the PHP version with $ php -v.

Even though that latest upgrade was a minor one, there’s always a possibility of a side-effect. You should access the site’s error log, probably through the control panel of your hosting, else by requiring it to hosting support.
It should display whether there’s an error in that image generation.

Hi

More details are required in order to efficiently help you. How is your site hosted, what are its version, plugins and theme ?

What have I done?

And that is the question. You say you *were* going to do an action in a section of the theme customization? Did you ? Which one exactly ?
By gone do you mean your site cannot be displayed anymore ? At all as in all pages are blank, or juste some of them ?

Infected files may be created through a server / files permissions issues, in which case you end up with the hack chain outside your database – injected in the footer.php file for example. If you have SSH access to your server (and if you don’t, your hosting provider will).
This is a tool made for Plesk but that works for any Linux server to help locate such a bad contents:

https://github.com/netagence/linux-injection-hack-fixer

Hope it helps.

The anti malware tools you mention are for a local PC, using them to check the issue did not come from a hacked machine (and stolen credentials) is required but not sufficient.

Still no replies to

“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 ?”

If i delete all content and data then all my SEO work is lost. so please suggest any other way to fix this…

Your SEO positions will in no way be lost if you temporarily delete contents and put your site back online even if it was suspended for 24h (use a plugin that lets you specify the site is under maintenance, 503 response). Getting your contents back online in a safe environment will on the opposite ensure that Google does not one day detect your site as hacked, and prevents people from visiting. Such a blacklisting from the main search engine may be much harder to get out of and prejudicial to your SEO efforts.

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

It also could. See your hosting logs for details, and check the hosting environment is up to date / compatible with the requirements of the WP you’re installing.