Hello,
I have two forms that up to a week ago worked fine. However, when I added a couple of fields, things changed. The Article Fulltext field empties upon save if the content longer, but it worked before. I've tried multiple editors and it doesn't work. I've tested it in Chrome, FF, Safari, and IE. It doesn't work in any browser. I've posted a standard joomla article with the exact article that won't post in seblod, and that works. I created a new form with just title and fulltext, and it doesn't work either. This issue occurred prior to updating to Joomla 3.3.1. The content literally just disappears from the editor. Can anyone assist?
Cheers!
Merkin
www.ourchart.org
Hi,
does it work if text is short? If only long texts dissapear you might be hitting some php ini limitation
It was working before though. This just randomly started happening for no reason. If this is the issue, what do I need to fix?
First you need to find a way to reliably reproduce this error. Does it always happen with certain text, or certain text length..etc - you need to find the trigger, then it will be easier to find the cause.
Okay. I found out that the sql introtext table was set as text and not longtext. We changed that on the server side. Is there a setting in seblod for this as well so I can avoid this issue? I appreciate all your help, Klas.
When you go to the introtext field storage, there is an option Alter. I presume somebody must have clicked that by accident as from there you change each column type.
Interesting. I've used that for integer columns, but I don't touch the core objects for fear of something like this happening. I'll keep that in mind. Thanks for the clarification and for the great freeware. We've purchased several of your plugins and I find your system superior to others. Thanks again!
Hi,
i had the same thing. Noticed it yesterday en couldn't find the reason. Also saw it when i took a look at the database. For me it was warchar 255...
I changed it to text (do i need a other option for the best result? Above is longtext mentioned but that wasn't an option.
I can't imagine i would have touched those core fields as i don't really need them for my seblod content types.But somehow it happened... Glad it works again and learned something new...
I changed it to longtext via the actual storage type in the phpmyadmin. It wasn't an option on the seblod alter. Hope that helps.
