Edit header and encounter error

asked Jul 30, 2012 by simonwai (220 points)
I tried to Edit a Header and once i click Save Content, it display the following error:

Oops! sorry but something fishy is going on - try again or call for support.

1 Answer

answered Jul 31, 2012 by Pavel Kovalyov (2,300 points)
selected Aug 2, 2012 by simonwai
 
Best answer
Hi simonwai,
is there any messages in php/apache error logs? Can you email us at support@seotoaster.com with attached logs if any?
commented Aug 1, 2012 by simonwai (220 points)
Hi Pavel,

I have enable error_log settings under php.ini but seems like no error is log. What did i do wrong here? hmmm..
commented Aug 2, 2012 by Pavel Kovalyov (2,300 points)
Check also if file that you used for error_log setting is exists and writable.
Plus, php.ini setting log_errors = On. And check error_reporting parameter value accoding to http://php.net/manual/en/errorfunc.constants.php
commented Aug 2, 2012 by simonwai (220 points)
Hi Pavel,

I have done what you have suggested, but i still don't get any errors log.  Any other clue? Btw, do we need to setup log folder for seotoaster like /htdocs/seotoaster/logs ?
commented Aug 2, 2012 by Pavel Kovalyov (2,300 points)
No, no separate logs folder needed.
Can you check in database if content you added is there?
Also please check sql mode with "SELECT @@sql_mode;" statement through phpMyAdmin or mysql console.
commented Aug 2, 2012 by simonwai (220 points)
here's the result:
mysql> SELECT @@sql_mode;
+----------------------------------------------------------------+
| @@sql_mode                                                     |
+----------------------------------------------------------------+
| STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION |
+----------------------------------------------------------------+

Also I do a query on
mysql> select * from plugin_netcontent_widget;
Empty set (0.00 sec)
commented Aug 2, 2012 by Pavel Kovalyov (2,300 points)
I just test with your parameters and also received an error.
So workaround for now is to switch off strict sql mode: just edit my.ini and add/edit line in [mysqld] section:
sql-mode=""

Like our facebook page to stay tuned for latest updates. We will work on toaster compatibility with strict sql databases and release update asap.
Thanks for your feedback.
commented Aug 2, 2012 by simonwai (220 points)
Thanks. This solve the problem on my side as well. Cheers
...