Marin Petkov
Forum Replies Created
-
Waiting for an update.
- This reply was modified 5 years, 8 months ago by Marin Petkov.
Yes, it’s quite frustrating.
I took me a while to investigate and resolve the case. I removed Wordfence and the error above appeared.
Then (via SSH) found .user.ini had few lines of code, which were “looking” for the file wordefence-waf.php, which I removed. Below you can see them:Wordfence WAF auto_prepend_file = '/path_to_file/wordfence-waf.php' ; END Wordfence WAF
You can either comment the lines or delete/rename .user.ini to resolve the issue.
Hey Moses,
I believe that was the issue above, however, since It isn’t my advice will to check your data base for mixed content.
I found an article to help you understand and resolve the mixed content situation – How to resolve mixed contentForum: Fixing WordPress
In reply to: The Appearance of Website Pages are all messed & brokenHey buddy,
Well, I am glad to hear It’s working now. For future I will advice you to either use the W3 Total Cache (even though It’s a bit heavy and requires more manual changes to work properly) or the WP Super Cache.
The WP Super Cache is kind of like the WP Rocket plugin – easy to set up and run, right away. ??Cheers!
Forum: Fixing WordPress
In reply to: The Appearance of Website Pages are all messed & brokenSince that is the case, I will advice you to contact the Technical Support of the hosting by submitting ticket to them.
Forum: Fixing WordPress
In reply to: The Appearance of Website Pages are all messed & brokenHello again,
You should search for https://https://troogs.com and replace with It “https://www.troogs.com” and you will also need to select all tables in the Better Search & Replace plugin.
Please, as well uncheck the “Dry Run” box.I assume that since you have “https” re-directions on your website, there should be “https://yourwebsite” URLs in the data base.
That’s how I found out there are “https” URLs.Hello friend,
The Elementor plugin has a lot of HTML code in It, however, the issue isn’t caused by the bigger HTML pages (content) on the plugin, but due to the fact Apache server configuration is configured by default to allow no more than 1MB of HTML page.
That can be easily solved by accessing the .htaccess file of your website and adding this at the very top of the file:SubstituteMaxLineLength 20m
The rule above will say to Apache to “allow” 20MB of HTML content to be loaded.
Please, clear your browser cache and verify the results on your end.
Forum: Plugins
In reply to: [Code Snippets] PHP Parse Error & Incompatible with Formidable FormsHello,
As I see the syntax error you get is most probably caused by “<” sign in the “snippet-ops.php” file, which is located at /home/mysite/public_html/resource/wp-content/plugins/code-snippets directory.
If your hosting is using cPanel as control panel, you will be able to access the the file from the File Manager tool or via FTP client such as FileZilla.
Once you access the directory of the file, download the file “snippet-ops.php” so you can have It locally stored on your computer as backup and then open the file (If you opened at File Manager, select the “Code Edit” option), then at line one (first file of the code) you should see “<” sign. Please, remove It, then save the changes, clear your browser cache and verify the results.
If that way the problem isn’t solved, you can upload back the “snippet-ops.php” file through the File Manager with the “Upload” button or through FTP.
Forum: Fixing WordPress
In reply to: The Appearance of Website Pages are all messed & brokenHello again buddy,
Apologies for the delay. Since you do not want to have SSL, but many of the URL resources are loading through “https”
, those “https://troogs.com” URLs need to be replaced with “https://www.troogs.com”That needs to be with the Better Search & Replace plugin OR with wp-cli (SSH) command.
- This reply was modified 6 years, 9 months ago by Marin Petkov.
Forum: Fixing WordPress
In reply to: The Appearance of Website Pages are all messed & brokenHello,
I see the WP version is 4.9.3 and I would like to inform you that It will be better to update to 4.9.4, If your hosting provider does not force the update.
That’s not related to your current issue, but due to security concerns and for your personal convenience.About the messed up content of the website:
Do you wish to have your website running with SSL or without one?
If you would like to have SSL, contact your hosting provider and ask them to install It (If they offer free SSL). Also, could you please share the URL of your website?Forum: Plugins
In reply to: [WooCommerce] bank transfer checkout Bad GatewayHey,
I am happy to hear this worked out for you, friend! ??
Usually, the PHP max. execution time is set to 20 sec. (at most of the web-hosting, shared servers). That’s why the 600 seconds dynamic timeout limit solves the issue.
About the delay in the submitting of the order – my personal advice will be to ask the hosting comapny’s technical support to check the MySQL server log for slower MySQL queries. A slower MySQL query is the one, which loads for more than 1 second.
- This reply was modified 6 years, 9 months ago by Marin Petkov.
- This reply was modified 6 years, 9 months ago by Marin Petkov.
Forum: Plugins
In reply to: [WooCommerce] bank transfer checkout Bad GatewayHello,
Usually, a timeout error appears due to lower value of the PHP maximum execution time. That’s the maximum time for which, the one process can be performed and If the process does not execute in that set of time, the server “cuts” It in order to continue with the next process.The solution here is to insert this in your .htaccess file of the website:
<IfModule mod_dtimeout.c>
<Files ~ “.php”>
SetEnvIf Request_URI “index.php” DynamicTimeout=600
SetEnvIf Request_URI “themes.php” DynamicTimeout=600
SetEnvIf Request_URI “wp-admin” DynamicTimeout=600
</Files>
</IfModule>This above is a way to dynamically increase the PHP timeout, because many hosting servers limit the execution time on shared servers to 30,60,90 or 120 seconds, which in many cases isn’t as much as the PHP process requires.
Please, clear your browser cache and verify the results on your end, after the rules above are applied on the top of your .htaccess.
The .htaccess file is usually located in the root folder of the website.