hi
I am not sure why, when I try to edit i get thrown in the CONTENT menu, whereupon when I again tr y to open a page, it just loads forever.
video here https://www.screencast.com/t/nV9geBYp
The previous behavior went straight to the CS builder, skipping the themeco CONTENT menu altogether.
help!
note: i just upgraded to php 7.4.
Regards,
Alfredo
Hi Alfredo,
Thank you for the information. Is this happening after you upgraded to version 7.4? Or it is something that was there before?
I suggest that you follow the general steps below:
kindly get back to us with the result of the steps above and URL/User/Pass of your WordPress dashboard using the Secure Note functionality of the post to follow up the case if you still have problems.
Thank you.
Hi
Thanks fo the procedure. I followed it, and was able to replicate it when re-enabling essential grid. Now… this is a plugin that I indeed hope to use, so I would love to fix the actual underlying issue.
Details on a secure note; can you please take a look?
Hi @flashfog,
It seems the Essential Grid is not really the issue. It seems to have something to do with a security feature. Would you mind turning off ModSecurity for a while and test if that resolves the issue?
Also, please try increasing your PHP Memory Limit to 512M.
Also, I see that you have a bit of customization on your child theme, would you mind removing that for a while and see if that resolves the issue?
Let us know how it goes,
Cheers!
Hi
Can you elaborate on why you think it’s mod security, not essential grid?
I just spend a while with tech support; here is what we know
-disabling mod security does not resolve issue
-enabling essential grid re-triggers the issue
-uppping memory limit does not resolve the issue
Regarding child theme customization :
the only css is;
/*
You can add your own CSS here.
Click the help icon above to learn more.
*/
body {
-webkit-flex-wrap: wrap;
flex-wrap: wrap;
}
.tooltip{
font-size: 24px; /* Increase or decrease number to achieve target size */
}
/* title /
.popover-title {
font-size: 24px; font-weight: bold;
}
/ content */
.popover-content {
font-size: 24px;
}
Frankly, i don’t see this can cause so much trouble. You are welcome to go in and disable… I am not 100% sure how to do this without braking things.
THANKS
Hi @flashfog,
That is because of this Connection: close status.
Commonly the connection is close because it’s being blocked, Though I’m not entirely certain that ModSecurity was the culprit (deactivating it was just a test), but I’ve seen this Connection: close on the past and ModSecurity was the culprit. Another possibility is you might have other security features.
I’ve tested it with the Essential Grid disable and I’m still getting that error.
The PHP memory limit on your site is still 256M, would you mind increasing that to 512M? Memory exhaustion can cause 500 Internal Server Error as you can see on my screenshot.
You have a custom function on your child theme.
function x_woocommerce_donot_remove_plugin_setting()
Would you mind removing that or switching to parent X theme for a while?
I keep getting this on your site
Do you think your DNS/server is acting up? We cant fiddle properly around on your site because of that DNS error keeps happening.
Thanks,
Hi.
Can you please explain where you are seeing that memoy is a 256 M only, because the hosting providers swears to me with all their might that its set at 512.
They say "512M, it was set in both the php.ini and the .user.ini. But I actually first checked phpinfo.php, it was 512 there too’
Regarding the function; would you mind showing me where in the customizer in find the custom functions?
Hi flashfog,
I was looking at X > Status > WordPress Environment, but you’re right when I check on Tools > Site Health > Info its 512M, please ignore this for now, we have this discrepancy bug before but this has been already resolved. We’ll check on this.
It’s in the Child theme’s functions.php file.
What did the hosting say about the Connection: close status? (screenshot above)
Thanks,
Hi
The issue seems resolved by rolling php back to 7.0. That being said, what could the problem be? I would hate to deal with this again down the line.
thanks
Hi flashfog,
Thanks for that info, we’ll investigate on that. But we’ve seen sites running with PHP 7.4 and does not have this issue. There could be another factor involved on this, one of that is security.
Cheers!
How would security force a re-direct? (the first sign there is a problem) Can you guys go through the change log between versions and check the changes: which could explain the builder failing to load?
Hello @flashfog,
Download the 4 index.php from the different folders to your computer. If you suspect a malicious code in the file, it should be unreadable or has been optimized in just one line without indention. A normal WP code in the file starts with:
<?php
/**
* A file description of what is this file about or how it will be used
*
*
* Some additional information and details of the or to the code
*
* @package WordPress
*/
/**
* Some function and code names, list, enumerations
*
* @since 1.0.0
*/
If you see { and some random-looking codes }in the file, you should delete that code block from { up to } until it will starts with the normal <?php code format that is used by WordPress.
From the looks of the file structure, those folders were not part of WordPress. It could mean that the initial load was injected or has been there prior to the hack. It could also be coming from a vulnerable plugin or outdated plugin.
Hope this helps.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.