mleder

Yes, putting the css in the theme customization panel did the trick. Thanks for your help.

• This reply was modified 1 year, 11 months ago by mleder.

Do I need to name custom classes for open/close?
I inserted the css in the custom field as you suggest, saved, purged all caches, didn’t work.

So obvious! Thanks for your help.

Thanks!

Put all the suggested code from the debugging article on the site, ran two test transactions, no errors thrown.

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

Transactions process, money is ported to payment processor, data is recorded as it should be in db, I get emails as I should. However, still no auto generated passwords, and the redirect is supposed to go to a “thank You” page, but circles back around to the sales page. Never did that before.

FYI – for the WF tables, I was able to correct the problem by setting a parameter to delete WF files, then deactivating WF, then reactivating, finally reset the parameters. My reply above did not pertain to WF specifically, sorry.

• This reply was modified 4 years, 10 months ago by mleder.

Deleted

• This reply was modified 4 years, 10 months ago by mleder.

Any comment on this? It’s still a problem.

Commented this line and it all worked.

# location ~* /wp-includes/.*.php$ { deny all; access_log off; log_not_found off; }

Now I have to figure out the right way to config this directive.

Thanks for your help.

I bet this is it, yet it works on all other WP sites (from my nginx file):

# prevent browsing to certain wordpress files
location ~* /wp-includes/.*.php$ { deny all; access_log off; log_not_found off; }
location ~* /wp-content/.*.php$ { deny all; access_log off; log_not_found off; }
location ~* /(?:uploads|files)/.*.php$ { deny all; access_log off; log_not_found off; }
location = /xmlrpc.php { deny all; access_log off; log_not_found off; }

But with regards to the error in my initial post, wondering how to make an exclusion?

I found the problem, one plugin that had bad code; I have since removed it, and no errors.

For the benefit of others, here’s an easy way to figure out where the wrong code is:
1) To your local dev machine, download the entire wp-content folder and all subdirectories.
2) I use windows, installed and ran Find and Replace.
3) Do an exact match find on ‘register_sidebar_widget’ from the wp-content dir. Include subdirectories. Exclude .log files.
4) Within a minute, crawled nearly 11,000 files and found three matches, all in one plugin.
5) Disabled the plugin on the live site. Clear the error log files. Browsed the site normally.
6) No more errors!

Thanks for your help.

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

No child theme being used with 2017.

Only thing different between this site and about a dozen others I host is this in the wp-config.php:

`error_reporting(E_ALL); ini_set(‘display_errors’, 1);
define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define(‘WP_DEBUG_DISPLAY’, true);’

Also all sites use common includes for php-fpm calls in the nginx configurations, in other words they are all structured the same.

Thanks for your insights on this!

Anyone??
I’ve turned off all plugins, checked the nginx configuration, don’t know what else to do.

Reinstalled 3.8.3 theme (overwrote). Same problem.
What is this theme4press plugin you’re referring to? Don’t see it on their site, nor in plugins search.