[solved] Error on opening /symphony/blueprints/datasources/
This is an open discussion with 12 replies, filed under General.
Search
Your database query stops at extension sym_documentation ... guess that is the suspect
Thanks for pointing me there, will have a look at that patient :)
Hmm, after uninstalling Documenter
(which threw an error as well, I needed to delete it form the db manually) the last query in the error log has become
SELECT SQL_CACHE `s`.* FROM `sym_sections` AS `s` ORDER BY `s`.`sortorder` asc;
Maybe it has something to do with the 2.5.1
cache-update? Will try upgrading.
Nahh, no dice :(
Hmn, opening the respective datasource-editors/info-pages via their direct url works fine. E. g.
http://…/symphony/blueprints/datasources/edit/[datasource-name]/ http://…/symphony/blueprints/datasources/info/[datasource-name]/
It’s only the list of datasources that throws the above error.
Just update an install and no problems. (not that helpfull I'm afraid)
?
Are references to datasources stored in SQL somewhere?
The error persists even if I temporarily move all my datasources in a different folder.
The error is occurring when generated an anchor for one of the datasources, here. It's expecting that all datasources will provide in their about functions at least the name
and handle
. Datasources generated by Symphony usually have this information, but custom ones may not.
My guess is that there is a custom datasource (or one provided by an extension) in your installation which does not have a name
in their about array. Does this ring a bell?
@brendo that was one hell of a bell you rang there! Actually it was the data.search_suggestions.php
provided by the search index
extension that was »nameless«.
Thanks a lot! My installation feels a lot healthier now :)
Create an account or sign in to comment.
I am unable to open the datasource page in the backend on a system running
2.5
(updated from2.3
). Searching the forum only yielded something about the »about«-functions in the datasources. Not sure if this is what happens here. Can anyone help me to find out what causes this?