716 errors upon activation
-
Hello,
following your advice to troubleshoot why my site becomes unresponsive after a few days with AntiBots, I installed Site-checkup that works fine and WP-Tools that generates 716 output errors on activation and keep displaying following PHP error several times on each backend page (I cannot see the beginning of the message hidden behind left column):
es not support seeking in /home/rjubpnsm/public_html/wp-content/plugins/wptools/functions/functions.php on line 1739
PHP is 7.4 actually
Thanks for any help
Eric Collart
The page I need help with: [log in to see the link]
-
Hi Eric,
Thank you for the information.
The error you mentioned occurs because the PHP
fseekfunction is not available in your server’s PHP. This function should exist, but I assume it was not installed by your hosting provider. To work around the problem, I developed a new version of wptools(5.09) that, if there is a failure in this line, does not record the error and gives up on that specific task, which is to read the end of the error file and analyze the last lines to get information about the date. I hope this work for you.Regarding the table formatting, it is built in JavaScript, which is the most suitable tool for this purpose. However, since your site has problems with JavaScript, the table may not work properly. In this case, to start solving the problems, I suggest you try using our site-checkup plugin where you can see the lasts errors without the table.
As I mentioned earlier, a JavaScript error interrupts everything that follows and causes problems, especially in menus, links, tabs, accordions, graphs, tables, etc.
I saw your site and found this JavaScript error in the console:superpwa-sw.js?2.2.21:119 Uncaught (in promise) TypeError: Failed to execute ‘put’ on ‘Cache’: Request method ‘POST’ is unsupported
at superpwa-sw.js?2.2.21:119:14
https://wptoolsplugin.com/how-to-identify-javascript-errors-using-the-browser-console/Regards,
Bill
Please, try the version 5.10
I am building a new version (maybe 5.12) that will identify the cause of the problem, for example, if the function was not installed on the server (by hosting), if the file is not readable (maybe damaged), or other issues. So, as soon as I have this version tested, within 2 days, I will let you know here.
Huge thanks for such reactive support.
Eric Collart
You are welcome.
Version 5.11 has been released.
The previous version (5.10) was merely an emergency fix to prevent a specific error from being recorded when the system was unable to read and navigate its error log. However, it did not resolve the underlying issue.
This new version can generate a comprehensive report of your server’s capabilities, such as whether it is configured to read (error) files and what else is needed to allow our plugins to function.
To view the report, simply go to the plugin’s dashboard and click “Debug Info.” Copy the contents of this window and post them on our support site. You will find the link at the top of the aforementioned window. After receiving your information, I will study quickly it and tell you what the problem is with your server’s configuration or work around it, if possible.
Ok, now your plugin is generated one line error on frontend what is not acceptable so i just removed the plugin from my website !
Just gave up as too complicated to use
I hope you’ll improve in future
Eric collart
Hi Eric,
Thank you for the information. I found out that your server does not support the PHP fseek function, which is an essential function for WordPress and cannot be missing. It allows you to “walk” through the file back and forth. I couldn’t find out if there are other functions besides this function, because I didn’t receive any more information from you, nor the line you said appears on the screen. On the other hand, I learned that your website has errors that need to be resolved, such as the ones below.
superpwa-sw.js?2.2.21:119 Uncaught (in promise) TypeError: Failed to execute ‘put’ on ‘Cache’: Request method ‘POST’ is unsupported
at superpwa-sw.js?2.2.21:119:14and
Javascript Message: TypeError: exportLogs is null – URL: /wp-content/plugins/simple-download-monitor/js/sdm_admin_scripts.js?ver=3.9.27 – Line: 5″
Our plugin does not fix errors, because if we intervene and modify files, everything will be lost in the next update, whether of a plugin or theme. But we help find them. The arrangements need to be made by the respective developers and your hosting, which should deliver a server compatible with WordPress. We managed to walk a little, but not all that was necessary, but let’s look on the positive side. Better to walk little than nothing.
Thank you and good luck with your site.
Regards,
Bill
Hello,
the line on Frontend was back yesterday and stayed present event after I deactivated wptools and still after uninstalling…
I was able to clear it by clearing the cache in place at hosting provider level. Clearing the cache from within WP didn’t clear it.
As I uninstalled wptools, I can no more add info to my opened guest ticket as there is no link to get there in any mail received from you. I tried to reply to one of those mails but the mail was not delivered (noreply mailbox)…
I have the debug info and 2 screenshots (backend activation result and frotend) to provide if still interested. In debug info it is noted that fseek is supported but not sure at what level…
I don’t want to install back site-checkup nor wptools as the latter is generating too much trouble; the latest version 5.12 still generated 537 output errors upon activation (that is already better than previous versions) and 4 PHP errors instead of 5
Here is the PHP configuration part of the debug info as there is no sensitive info there:
— PHP Configuration
PHP Memory Limit: 512M
Upload Max Size: 32M
Post Max Size: 128M
Upload Max Filesize: 32M
Time Limit: 360
Max Input Vars: 200000
Display Errors: On (1)
Fopen: Supported
Fseek: Supported
Ftell: Supported
Fread: Supported— PHP Extensions
cURL: Supported
fsockopen: Supported
SOAP Client: Installed
Suhosin: Not Installed
SplFileObject: InstalledHoping this can help
Eric Collart
PS: I opened a ticket with SDM and they corrected the error in latest version so that error was no more generated after plugin was updated.
I will do the same for SuperPWA team and we’ll see…
The error related to SuperPWA is known and will be fixed in next version (no date given); their support said this error can safely be ignored.
Eric
Hi Eric,
Thank you very much for the information. It was very useful.
From what I saw, the hosting has the necessary resources activated (at least now), so those problems with PHP fseek are not justified.
Some suggestions, regardless of whether you have deactivated our plugins: 1. Update the version of WordPress to 6.7.2. (they fixed 35 bugs).
2. Keep an eye on the site’s cache. I’ve had many problems with cache on my server and it seems to do strange things.
3. Keep an eye on the fact that a plugin has “disappeared”. It could be (I hope not) that a hacker is getting into your system. Or the hosting could have removed it without warning. Or anything else not good.
That’s all I can tell you, I hope it’s useful.
We not removed you from our site. You can come back whenever you want. You can even log in as a guest, without needing to register.
Good luck with the site.
Bill
Hello,
No plugin disappeared (site-checkup), I checked the logs and I did it but not remembering because I didn’t note down that action… Hopefully no hacker….
I updated WP to 6.7.2 and clear cache at all levels I can (Firefox history, WP Litespeed cache and LScache at hosting level) …
I will wait some days or weeks to let my site looking stable again and probably retry your very interesting plugins and let you know how it goes… Good to know my guest ticket will stay available for update…
Thanks for your efforts and responsive support
Eric Collart
The topic ‘716 errors upon activation’ is closed to new replies.