You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The extension does not create a ("dummy") table for the static section field. The missing table causes errors in the logs each time the datasource is called (no matter if the field is included in the datasource output).
I wouldn't mind having an empty table in the database. The logic simply is "each field has a table".
The text was updated successfully, but these errors were encountered:
I made some experiments using the current integration branch of Symphony. Things are even worse then, because Symphony will throw error pages like the following:
Symphony Fatal Database Error
Table 'wwwsymphony_dev.sym_entries_data_362' doesn't exist
An error occurred while attempting to execute the following query
SELECT * FROM sym_entries_data_362 WHERE entry_id IN ('11339') ORDER BY id ASC
...
That sounds pretty nasty, thanks for looking into it for me concerning the integration branch (which I've never had the time to play around with).
I actually had this same issue raised by rainerborene on the forums some time ago so had since removed my improper "empty table" override in all my local versions, but hadn't had the time to push back here to github.
Thanks for performing the fixes for me and providing the pull request, I'm not very experienced with Git but I believe I've merged your changes successfully, please let me know if you believe this isn't the case.
The extension does not create a ("dummy") table for the static section field. The missing table causes errors in the logs each time the datasource is called (no matter if the field is included in the datasource output).
I wouldn't mind having an empty table in the database. The logic simply is "each field has a table".
The text was updated successfully, but these errors were encountered: