I've updatted to Views 3, because Views SOLR required it and I am working in multisite environment without problems. Only one of the sites make problems when submit node. The pictures in CCK fields are not uploaded and DLOG throws this error:
Warning: require_once(./sites/all/modules/views/includes/query.inc): failed to open stream: No such file or directory in views_include() (line 554 of /public_html/sites/all/modules/views/views.module).
I don't have such file query.inc in includes folder of views. When I submit the node, the CCK images are "undefined" and imagecache don't generate them. If I edit the node I can see, that the attached files are missing. When I upload them again, everything works fine. But every time I need to edit the node to make it look correct.
Please, tell me what I can do to fix this error? Thanks!
Comments
Comment #1
merlinofchaos commentedgrep your modules for the line "views_include('query')" and see where it's coming from. The most likely possibilities are:
1) An incomplete upgrade has some old code merged with new code
2) One of the modules you have using Views is only compatible with Views 2.x and has not upgraded to be compatible with Views 3.x
Comment #2
Terko commentedI usually overwrite with WinSCP the folder, but maybe this is not good idea. I will delete and upload again the views folder.
Comment #3
Terko commentedI found this code in Boost module:
Do you think that it's safe to comment this function?
Comment #4
dawehnerSo
Comment #5
Terko commentedResolved the problem with unchecking the option in Boost "Clear all cached views pages associated with a node on insert"
Thanks merlin!
Comment #6
merlinofchaos commentedLet's put this back to Boost since it could probably fixed with only a couple lines of code there.
Comment #7
mikeytown2 commentedI haven't used views_include() in the boost dev for some time. Hopefully in about a week or so I'll release Boost 1.19; got it running on A LOT of domains and there might be a couple small bugs to work out before I christen the next version. I'll mark this RTBC till I release 1.19
Comment #8
TimelessDomain commentedduplicate issue #696216: Fatal error causedd by a require once not being honored or so it seems
Comment #9
chuckbar77 commentedsubscribing
Comment #10
brycesenz commentedsubscribing.
Comment #11
mrfelton commentedsubscribe
Comment #12
bgm commentedCan someone confirm if it is fixed in 6.x-1.x dev snapshots?
Comment #13
bgm commentedNo feedback, closing the issue.
Comment #15
SchwebDesign commenteddoes anyone know if this was "actually fixed" or do we need to continue