Digital experiences for all disciplines
New Landing › How can we help? › Cardinal › Post Not Saving Meta Options
New Landing › How can we help? › Cardinal › Post Not Saving Meta Options
- This topic has 76 replies, 7 voices, and was last updated 9 years by Rui Guerreiro – SUPPORT.
-
Posted in: Cardinal
-
April 14, 2015 at 1:59 am #164897
Hi @George
No, nothing has been changed by us.
Rui will get back to you tomorrow on the meta options issue.
– Ed
April 14, 2015 at 5:19 am #164917Hi Ed,
Thanks for that, must be some kind of host issue (we’re going to change our hosting).
As for the meta options issue Rui, i’ve been testing and it appears that when copying across content from my saved template, using the shortcut or copying physically from elsewhere, the meta options do not save to begin with, however after deleting rows (almost half) the options suddenly save.
Could this be some kind of data size (amount of content) of the content inhibiting the meta options saving?
Thanks,
George
April 15, 2015 at 1:57 pm #165338Hi,
Apologize wasn’t possible to check it yesterday.
At the moment is saving fine. It’s half the content at the moment?
Can you leave it in the situation where it doens’t save?I also tought abouth something regarding the content size.
Can you do an experiment an place half of the post content that is problematic in an SPB Section, than include that SPB section inside the post content.This way the post content will have less content and we can figure out it the size is the problem or something in the content itself.
thanks
-Rui
April 15, 2015 at 11:43 pm #165496Hi Rui,
So i followed your advice, i opened up the test post, and the saved template (where meta options don’t save) and slowly removed content and put it into a row on another post). I got down to having 11 rows left, from the saved template and the meta options suddenly save. So 11 appears to be the magic number that lets me save.
I then took all the deleted content that i put into another row on another post and then added that into the test post. This now makes 12 rows (technically all the content is there) and the post options did not save. So this means that with all the content even in 12 rows the meta options don’t work. I then deleted one of the rows (so it’s got all content within 11 rows (less a row) and the meta options did not save.
So i’m concluding basically that it’s the amount of actual content, not the amount of row sections that causes the meta options to not save. It doesn’t matter what content, just a certain amount.
Feel free to test this yourself, the saved template is called NWC 2015. with all the content there, meta options don’t save, unless you delete about half and it suddenly saves.
George.
April 20, 2015 at 12:37 am #166287Hi,
After several tests, I also manage to replicate in your server what you described.
So I tried in mine, and everything worked fine with the biggest content.I read again the topic from the beginning to see what could we miss, and just realized we didn’t used yet the ftp access you provided us last week.
Your error_log is about 28mb , you should rename it to stay has backup and create a new one so it can be easily opened if necessary.
The answer was inside the error_log, you have several database errors among other errors.
The error indicates that you server is running out of disk space(what makes sense).
Check this situation, and hopefully reply us saying that is all fine after increasing the space 🙂
-Rui
April 21, 2015 at 3:05 pm #166941I am having an issue updating the posts as well. If I put too much content into a post using page builder it stops updating the content.
April 21, 2015 at 3:23 pm #166947April 21, 2015 at 3:44 pm #166952Hey,
Is there any other related reason? Our serve def. has enough space.
April 21, 2015 at 3:51 pm #166955Check the server logs so we can have more information. Database space is a bit different than the disk space.
Also try to deactivate all plugins and test again to discard any possible conflict.
Maybe it’s better to open a new topic.
thanks-Rui
April 28, 2015 at 6:15 pm #169676Hi George,
Did you manage to check this situation further?
Thanks-Rui
April 28, 2015 at 6:30 pm #169680Yes, I solved the issue. What I noticed is when page builder is used on a post and then updated… it treat every single page builder block as being apart of FORM. That can increase the size of the payload by more than 5 times. The problem that occurs then is that it will go past normal max_input_vars limits. So, the solution I did was to include some javascript to wipe out the data inside the page builder when our editors select the save or update button. This works very well and causes absolutely no issues. The post also saves much faster because it isn’t having to save/upload so much unnecessary data.
April 28, 2015 at 7:14 pm #169692@ shism2
Can you provide us that code? We truly appreciate if you can send us the code.
Thanks-Rui
April 28, 2015 at 9:12 pm #169716This is all I put:
jQuery(‘#publish’).click(function(){
jQuery(‘#spb_content’).html(“”);
});inside /public/wp-content/themes/cardinal/js/sf-admin.js in the jQuery(function(jQuery) {
April 28, 2015 at 10:53 pm #169744Thanks for sharing. Nice solution.
-RuiApril 29, 2015 at 1:48 am #169763Hi Rui,
I think the problem was my host and having space issues, or being overloaded.
I have since upgraded to a better host and the problem seems to be fixed.
Will let you know if it reoccurs.
Thanks for the ongoing help and support.
George.
-
Posted in: Cardinal
You must be logged in and have valid license to reply to this topic.