@jonmifsud Thanks for you help. I'll try to contact the dev again and hopefully get that set up.
Hi I am back with the same issue as yesterday I was unable to get in touch with the dev and I am unable to give a different title tags and meta descriptions to each page and I am also unable to get a text module to appear on site I see this error every time
Are you uploading files to the site via FTP?
@RonVargas01 that's a server configuration issue
Ok thanks I work for an seo agency and we have never worked with this system if there is someone who would be able to make these changes or show us how to please contact me so we can further discuss
Hello Ronald, please ping me via direct
May Kittens Devour Your Soul
is it ok if I axolotl questions?
yes this is what the channel is for !
I get this error trying to run a Symphony 2.6.3 site on PHP 5.6 / MySQL 5.7
Thanks @jonmifsud what exactly does that mean? Malformed data in the database?
& to & somewhere or something similar not sure if you may need an update of symphony. If you debug the page (assuming you can login to backend you may pick it up
Hello all, I'm using the Association field to store data on a member, but when I update the value using an event it removes all items except the new one. The field name is set up like fields[handle]which should allow for multiple values, but it's still stripping out existing ones. Does the Association Field need to be treated differently? I thought it was a multi selectbox behind the scenes.
@pixelninja When you update the value you should send all existing values also..
Greetings everyone! I updated a multilingual page (the relevant extensions: “Field: Multilingual Text Box”, “FLang detection gTLDs”, “Frontend Localisation”, “Languages”, “Page Lhandles”; Symphony and all extensions up-to-date) with Arabic (till then only left-to-right languages: German, French, Spanish, and English). This lead to an Symphony Fatal Database Error after filling the Arabic part of the text box and trying to save: “Data too long for column 'handle-ar' at row 1”. Going back and only keeping a few Arabic words within the field however worked out: saved successfuly. Guessing it may be due to the particular charset range I then tested with the full text from the German tab which interestingly enough also lead to the same Fatal Database Error. Only keeping a few German words in the Arabic field worked again. Anyone encountered such a behaviour before?
@Lindworthy Do you have the latest version of all extensions you are using?