Could be ezsession table issue, where you had filled up your ezsession table so new sessions couldn't be created and someone or php session gc being triggered somehow manually or automatic that fixed it. In recent versions there are both scripts and cronjobs to purge sessions manually if your on a Debian/Ubuntu based system where this doesn't work automatically.
Could be ezsession table issue, where you had filled up your ezsession table so new sessions couldn't be created and someone or php session gc being triggered somehow manually or automatic that fixed it. In recent versions there are both scripts and cronjobs to purge sessions manually if your on a Debian/Ubuntu based system where this doesn't work automatically.
I had tried that too. One of the answers to a similar thread suggested truncating the ezsession table. I remember truncating the ezsession table but that hadn't helped then.
I am running the latest version of ezpublish (4.4) and I am running it on windows. So, I doubt if this caused the error. Are there any other possible causes for such an error.
Why don't you add these tables? They should be in the sql directory of ezfind. I think they were added with the last ezfind upgrade. Probably someone forgot to do this when upgrading.
Indeed, the ezfind_elevate_configuration table was added in eZ Find 2.1. One can find the dump in the master branch there : https://github.com/ezsystems/ezfind/blob/master/sql/mysql/
Cheers,
--
Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board
Thanks. This did work. I added the ezfind_elevate_configuration table. This did solve that error but now i get a different one. The error that I get now is -
eZFindElevateConfiguration::pushConfigureationToSolr: An unknown error occured in updateing Solr's elevate configuration.
I searched to find a fix for this error and I found that I need to find an update for Solr too. I am looking for the update. Meanwhile, can help me find an update for solr?
