Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By IreneKraus on
I noticed the other day that on every install of Drupal 5.10, that the version number is not displaying in the log records in a consistant manner. For example, on an install on a live site it shows as the proper version number in the display of the Upgrade module, but in the Status report it is still saying it is Drupal 5.9. I did a fresh install on my development platform of Drupal 5.10, and - on this - it is showing the wrong version in both places! Very odd!
Guess I can't add screenshots to this message...
Comments
Contributed module at fault
In further testing on this, fault is most certainly within a contributed module as core Drupal v5.10 shows proper facts in Status. Got it down to one or more of the following:
DHTML menus
JQuery update
Views
ACL
CCK
Devel
Token
External Links
In other words, those very based add-ons most people put into a site! Going to take me a few days to work out which of these is the cause.
Irene Kraus a.k.a. The Computer Lady
Design COMP - www.design-comp.com
Irene Kraus a.k.a. The Computer Lady
Views Module corrupting Status for Drupal 5.10
I have been able to confirm that the Views Module is corrupting the display of the 5.10 Drupal status screen. If it was installed on a site prior to the upgrade of Drupal, and with the new Update module installed at the same time this is all it does. Version number does show properly in the Update module. More serious issue appears to exist when attempting a new install of Drupal using the 5.10 set.
Irene Kraus a.k.a. The Computer Lady
Design COMP - www.design-comp.com
Irene Kraus a.k.a. The Computer Lady
Views Module issue with Drupal 5.10
hi Irene,
i upgraded my site from Drupal 5.6 to Drupal 5.10 , everything is working fine, except View_fusion module. i think problem is in View module, View module (view_query.inc) is responsible for building query for view. it is building false query for fusion view, all views are working fine. i hope u solved it.
Kamlesh Patidar
Same from 6.3 - 6.4
Irene,
I am having the same issue with upgrading from 6.3 to 6.4, it keeps telling me to upgrade when I already have the latest upgrade. I hope someone could help us out. Im not exactly sure what the issue may be, but it could be a module like one of the repliers mentioned. However, I still have yet to do some testing on that aspect.
Best Regards,
------------------------------------------
Alvin Crespo
Interactive Developer and Designer
Not Views Module...
Okay, in case this wasn't made clear in my posts earlier... The fault - in my case - was not Views at all. What I found, after a LOT of frustration and testing, was it was caused by a combination of several factors.
When I first installed Drupal, the advice I was following came from a book on Drupal 4.x environment, and not that for Drupal 5.x. So, I was putting all of my contributed modules into the same directory as Drupal core modules. This is forbidden in Drupal 6.x, but is still permitted in Drupal 5.x; but many contributed modules released for Drupal 5.x and later will expect those to be under the sites>all>modules directory. When I did figure this out (took months!) and started moving the modules over to where they had to be, I made the mistake of duplicating some of the core Drupal modules into the one for contributed. This, in a nutshell, was behind my whole 'corrupted version' issue. Unfortunately, I could not figure out where or how to change the database pointers for those core modules, so I had to do a complete rebuild to fix the problem. But, I've had it up and running in Drupal 5.10 for a few weeks now with all version numbers showing everywhere as correct so I know I got that resolved!
In trying to sort this out, I did do a test install of Drupal 6.x, and did find many of the commonly used contributed modules were causing a number of odd behaviors. For example, on very important key module on my own site is the Image module:
http://drupal.org/project/image
This is still considered an alpha module for Drupal 6.x, and I could see where it had major problems! So, that's about as far as I'd gotten in so far as working with Drupal 6. As soon as I get some more free time, I fully intend to get back into testing with Drupal 6. If anything else, I hope my 'bug' reports and so forth will help get so many of those modules now in alpha, beta, or release candidate status into full release status. (So all of us can upgrade!) No, my knowledge of PHP isn't the greatest (about enough to make me dangerous!). Testing stuff out, though, that I can do and track which modules might be conflicting with others, etc.
Irene Kraus a.k.a. The Computer Lady
Design COMP - www.design-comp.com
Irene Kraus a.k.a. The Computer Lady
you are right
yes neither view module is creating problem, nor view_fusion. if you are using view_fusion then first check out the relation between 2 fused view, is it correct or not.
kamlesh Patidar