diegora

I should have phrased it better tbh. It wasn’t a ModSecurity “problem”, ModSecurity was blocking it for security reasons. Since it doesn’t seem like it’s happening only to me, that should probably be looked into, a widget shouldn’t be auto-blocked by ModSecurity. Thanks.

In my case it was a ModSecurity problem. Contacted the hosting company and they diagnosed and fixed it.

Failed to load resource: the server responded with a status of 404 (Not Found)

Just this.

PS: Yes, widgets.php exists in /wp-content/

There is one basic error in the console:
GET https://xxx.xxx.xxx/wp-admin/customize.php?return=%2Fwp-admin%2Findex.php 404 (Not Found)

I also enabled the debug log and tried to access “Customize” a few times but nothing shows up, debug.log is around 1 year old with old errors not related to this.

Done. Nothing changed. Problem persists.

Yes, the problem still happens when all the plugins are deactivated and ONLY SiteOrigin Widgets Bundle is activated.

WordPress 6.1.1
SiteOrigin Widgets Bundle 1.45.0
SiteOrigin North 1.19.13 (that’s what it says in the files since WordPress admin panel doesn’t give you a theme version, but it says it’s up to date)

Theme is SiteOrigin North

WordPress, Theme and Plugin are up to date.

edit: Just to be more clear, this didn’t happen before, I used to access “Customize” without any problem with the same plugin and theme. It’s been a long time since I had to access Appearance > Customize so I don’t really know when this started to happen.

• This reply was modified 2 years, 3 months ago by diegora.

I’m not using the paid version of the plugin and that’s why I’m posting here.
You obviously know the code can be easily applied to a regular field on the “free” version of the plugin, and the field can be hidden with some basic CSS, the “Hidden field” on the pro version is not required for the code to work.
Could you please answer the question?
Thanks!

I’m getting this PHP error
[11-Nov-2021 13:25:33 UTC] PHP Fatal error: [snuffleupagus][0.0.0.0][disabled_function][drop] Aborted execution on call of the function 'popen', because its argument '$command' content (cd '/home/tsmtecbr/public_html/PMAL/wp-content/updraft'; /usr/bin/mysqldump --defaults-file=4f956f6b026f01de6ecf6b1966ab6597.tmp --max_allowed_packet=1M --quote-names --add-drop-table --no-tablespaces --skip-comments --skip-set-charset --allow-keywords --dump-date --extended-insert --where=option_name=\'siteurl\' --user='tsmtecbr_wp92' --host='localhost' tsmtecbr_wp92 'wpvh_options') matched a rule in /home/tsmtecbr/public_html/PMAL/wp-content/plugins/updraftplus/class-updraftplus.php on line 1666

Hi, sorry but this is not the reason. I’ve already followed all the article instructions, including leaving the updraft page open. DATABASE backups still fail. Updraft is backing up a BIG uploads folder (10gb) without any problem. The last successful backup doesn’t have the “failed sql_mode” message as shown above. After the last successful database backup, the hosting provider had disabled some functions like proc_open that prevented Updraft from even starting, that was already fixed but I never managed to get the database being backed up again, can you please address this message in the log
4875.156 (4) Couldn't get the sql_mode value (N;); will not attempt any adjustment
if it’s a normal message and guide me through solving this, cause it sure looks like it’s related to the Database, which is exactly what is failing to backup.
Please help, thanks.

https://pastebin.com/dVJpLrW6

The backup works pretty well, including backing up a huge uploads folder, it always fails to backup the database.

[Moderator note: Please, No bumping].

• This reply was modified 3 years, 4 months ago by Steven Stern (sterndata).

Hi,
Updated. Same results still happening.

4874.964 (4) Saving backup status to database (elements: 31)
4875.081 (4) Resuming creation of database dump (WordPress DB)
4875.156 (4) Couldn't get the sql_mode value (N;); will not attempt any adjustment
4875.282 (4) Testing potential mysqldump binary: /usr/bin/mysqldump

HELP?
PS: Maybe some other function was also disabled by the server admin other than the proc_open that I already asked them to re-enable?

proc_open was disabled. After it was enabled in the server, Updraftplus can now start and backup everything EXCEPT the database.
Here is the log:
https://pastebin.com/NcmXC0Kt

• This reply was modified 3 years, 6 months ago by diegora.

Just got an error email from wordpress after I tried to start a backup yet again.

An error of type E_ERROR was caused in line 1731 of the file /home/tsmtecbr/public_html/PMAL/wp-content/plugins/updraftplus/class-updraftplus.php. Error message: [snuffleupagus][0.0.0.0][disabled_function][drop] Aborted execution on call of the function ‘function_exists’, because its argument ‘$function_name’ content (proc_open) matched a rule

• This reply was modified 3 years, 6 months ago by diegora.