I upgraded my blogs to 9.1.3 from 2.1.3 I believe it was, after numerous errors I eventually removed all the database entries of the blogs meaning I lost my previous members blogs, and now the blogs module still states
"This module is not correctly installed, the files are version 9.1.3, but the database is version
The site administrator needs to correctly install the module."
I also deleted all related blog fules re-uploaded and still the error persists, this is after I deleted the site cache.
Please enter your server specs in your user profile! 😢
The only reason it should give that error on upgrade is if you haven't upgraded the module after installing it - there are database changes.
If it's happening on a fresh install, then something else is wrong in your system whether that be cache or that you hadn't uninstalled the previous version.
On a completely fresh install, with a deleted cache, no database entries for a blog I'm faced with the error above, this is an almost empty dragonfly system, I just did this on a test site.
Please enter your server specs in your user profile! 😢
PhoenixOffline
Joined: Mar 18, 2004
Posts: 1543
Location: Netosphere
Well, I can't explain it - Blogs just does a simple check with the cached active_modules list and compares that against it's internal version - if they don't match, you get aversion error.
Sorry it was version 2.0.99.52, which I just installed again, and is now receiving the same message, I'm going to try completely deleting everything related to blogs and start from scratch. I think I actually had this problem previously and managed to solve it.
Please enter your server specs in your user profile! 😢
Sorry to bang on and post again, but another completely fresh install and the same thing is happening, before I installed I made sure there was no blog fields in the database, also deleted the cache system and every file related to blogs.
I then uploaded and clicked on install, got the usual your installation was successful, clicked on blogs and can't access then as its apparently not got the correct database version.
Please enter your server specs in your user profile! 😢
PhoenixOffline
Joined: Mar 18, 2004
Posts: 1543
Location: Netosphere
Not bizarre at all - it quite sensibly insists on being activated so that it can verify that it has been correctly installed. In order to check the module has been upgraded, and many admins do fail to install updates correctly, it checks against the cached active modules, rather than waste an extra database query. IMO, if all modules were setup like this, it would save developers a lot of wasted time.
However, the original concept is slightly flawed in its approach. In the next release, I shall modify the code so that it first tells you that it needs to be activated to carry out some checks. Then if the version is unsatisfactory, it will tell you to install/upgrade the module correctly before it can proceed.
Attachment:
blogs_install1.png
Description
Filesize
1.39 KiB
Viewed
9 Time(s)
You are not allowed to view/download this attachment
Attachment:
blogs_install2.png
Description
Filesize
2.27 KiB
Viewed
10 Time(s)
You are not allowed to view/download this attachment
