Forum Replies Created
-
Posts
-
You are right, Rikard. I thought I had changed the padding on the small version, but apparently I didn’t save propery. Thank you.
Thanks, Victoria. I did all the solutions suggested in the post, but to no avail. I’m thinking our server isn’t set up properly. We are going to move to a new provider soon.
With the latest update, I can’t add or edit sliders. I can work on them, it says they are saved, but if I back out and go back in, they are identical to the original. I used to be able to at least use the functionality provided through the Enfold theme, but it doesn’t work anymore.
Thank you all for your help. After pestering our support staff, they FINALLY looked at the server and noted that the security settings on the server were triggering a CAPTCHA every time a form fill was submitted to the wp-admin file when it isn’t the primary folder in the link, which is what happens on sub-sites using a sub-folder structure. They added an exception for this folder and my issue has been solved.
I love support staffs that say “It’s your problem. It’s your problem. It’s your problem…oh, it’s our problem.” :)
Rikard, I finally got my SysAdmin to change file permissions for all files and I’m still seeing the same 403 error for the admin-ajax.php file, but only on two of the four sites in my multi-site. The main site and the second site don’t throw this error, but my third and fourth do for every page.
EDIT!!!!!
I have discovered the trigger for this. ANY TIME I try to add an attribute to a tag in the “text” tab of the text editor, such as style=”font-size:24px” or class=”myClass”, it crashes the post. I have tried it with double quotes and single quotes. ANY type of attribute to a header tag or paragraph tag, etc., causes a 403 error to /wp-admin/post.php. Then, reloading the page gives you a 403 error to /wp-admin/admin-ajax.php.I never had this problem until the last few months.
EDIT AGAIN!
I’m finding other triggers that cause it to happen. That one is big, but there are others. I can’t for the life of me put together why it’s happening. I’ve made the temp admin account a super user and included the test page I’m using. At the state it’s in, it will save fine. The second I try to add anything else to it, it crashes.Thanks, Rikard. My apologies. I thought commenting on the ticket with the same issue was the protocol.
I am looking into the file permissions issue. This seems to be the culprit. I’ll comment back after my support team helps me solve the file permissions.
I am facing the same problem on a multi-site build. It has been appearing on a sub-site built as a sub-folder. Currently, it only is happening on my front page of the site listed in the private content.
I have done the following:
- Completely deleted the Enfold folder from the themes folder and uploaded the latest Enfold download via FTP
- Deactivated all plugins
- Removed and extraneous functions.php code from my child theme
None of these fixed the issue. I have tried refreshing the page, but this doesn’t solve it.
I have found if I move back my revisions one step, I can at least get the Advanced Layout to show up and I can make ONE edit. Then the issue happens again.
Thanks, thatryan!
It boggles my mind why the main Enfold functions.php file should add a version number to the child theme style.css file. This is what prevents it from auto-updating without a force-refresh or clearing your cache, which no one should have to do. That is the POINT of the version number.
I have removed this hard-coded “2” from my child theme’s style.css file by adding the following code to my child theme’s functions.php file. Again, I did not alter the main Enfold functions.php file. I did this in my child theme’s functions.php:
$child_theme_url = get_stylesheet_directory_uri(); $theme_num = wp_get_theme()->get('Version'); wp_register_style( 'avia-style' , $child_theme_url."/style.css", array(), $theme_num, 'all' );This allows WP to get the “Version” number you list in the top comments section of your child theme. By updating this number, you will now be able to have WP recognize your version number and auto-load the newest stylesheet version.
I would certainly like to hear from the Enfold team why they would hard code that version number ‘2’ for any child theme. Is there a reason why you would do that? Does using the version number from the child theme stylesheet cause issues with Enfold? I can’t think of a reason why myself, but I would be happy to be enlightened.
Okay, total “face palm” moment. I have a multi-site WP setup. I was adding the functions.php code to the wrong child theme. Total user error here. Sorry!
Ugh. This turned out to be my fault. To override the title text, a previous hack had me add some lines of code to the single.php file for the main blog. After cloning this page into my child themes and removing the line causing the problem, the issue cleared up.
Attached is a temp login,
Here is the situation:
- This blog is a secondary blog in a multisite build.
- The main page is supposed to be the main blog page
- I can’t get the Enfold title bar to show on the main blog page without specifying a page in the Enfold controls
- I have created a page and used the “blog posts” widget in the advanced tools
- I have selected that page as the Frontpage settings
- I have found that the /blog/ link issue is resolved if I also select that page as the “blog display” page. However, the pagination doesn’t work correctly with it set this way
- With this setting, each pagination page still shows the most recent posts at the top rather than moving to the next group.
- Instead they are added to the end of the list
So, I can solve the /blog link issue by selecting the blog page in the “blog display” setting as well as the Frontpage setting. But, that makes the pagination break. It seems I have to pick one or the other.
Thanks for taking a look.
Thanks, Andy. I’ve already checked them and there is nothing additional there. I’ve swapped back to default, saved, and still had the same issue. I went back to Post name and still have the same result there. Again, the title link is fine on the main page, but not on a single post page.
