This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Heute stehen keine Supporter zur Arbeit im Werkzeugsatz-Forum zur Verfügung. Sie können gern Tickets erstellen, die wir bearbeiten werden, sobald wir online sind. Vielen Dank für Ihr Verständnis.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
| 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
Dieses Thema enthält 25 Antworten, hat 2 Stimmen.
Zuletzt aktualisiert von vor 4 Jahren, 5 Monaten.
Assistiert von: Christian Cox.
After installing the Duplicator clone on my local site, I have been unable to reproduce the problem so far. I'm attaching a screenshot here so you can see the local results. The conditional is in place, and all the shortcodes seem to be rendered as expected. This is curious, so I visited the test site to get more details about the problem. The Content Template on the test site only had one shortcode inside the conditional - the company phone number. I was not able to see the problem. So I tried to add a few more fields to reproduce the error, but the site became unresponsive and now I neither load nor edit this Leader Manager post:
versteckter Link
Nor can I edit this Content Template:
versteckter Link
After several minutes, I get a 502 gateway error from nginx. Can you check to see what might be happening? If possible, we should check the server logs to see what could be happening on the server, why everything is so slow, and why we cannot edit this post or this template. If you are not familiar with server logs, I can show you how to activate them temporarily. Go in your wp-config.php file and look for
define('WP_DEBUG', false);
Change it to:
define('WP_DEBUG', true);
Then add these lines, just after the WP_DEBUG line:
define('WP_DEBUG_LOG', dirname(__FILE__) . '/error_log.txt');
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
define('WP_DISABLE_FATAL_ERROR_HANDLER',true);
Try to edit the Content Template or the Leader Manager post again. If any server-side errors are triggered during this process, it will create an error_log.txt file in your site's root directory. Use FTP to look for the error_log.txt file, usually in the same directory as wp-config.php. You may need to click "Refresh" in your FTP browser to see a new file appear. Please download this file to your computer, open it in any text editing software, and send me its contents. Once that is done, you can revert the changes you made to wp-config.php and delete the log file using FTP.
