homepage started listing nodes in wrong order

By nig on 14 Aug 2006 at 20:16 UTC

My homepage has started listing nodes in Chronological order, instead of reverse chronological order.

This has only just started happening and only happens when you are logged on - anonymous users still see the correct order (reverse chronological). You log on, it is wrong, log out again and its correct again.

What is going on??

Thanks
www.healheadingley.org.uk

Comments

any ideas on this? Many

nig commented 15 August 2006 at 06:49

any ideas on this?

Many thanks

it still doing it any

nig commented 15 August 2006 at 16:38

it still doing it

any suggestions on diagnosing the fault?

Sorry if this is a dead simple thing that you have all covered ages ago........

Many thanks

The problem appears only for

jase951 commented 17 August 2006 at 12:31

The problem appears only for current users and NOT new users.

This affects users with "administer nodes" access, meaning this is a core bug.

Same here - help would be appreciated

BlueNC commented 16 August 2006 at 13:20

My newest posts are appearing at the bottom of the last teaser page. Posts on teaser pages (like the front page, /blogs, or /blogs/{x}) are showing up in increasing node order, with the smallest node number at the top. There are a few exceptions, like nodes with much higher numbers appearing in the first few pages, but the general structure seems to be highest node numbers last. This results in something very much like chronological order.

I woke up to user emails about this this morning. Any ideas?

oh dear, it seems I'm not

nig commented 16 August 2006 at 18:17

oh dear, it seems I'm not alone

Your analysis of the problem is better than mine though.

Has anyone resolved this

0utlier commented 16 August 2006 at 18:17

Has anyone resolved this issue. This just happened to me too.

Same thing...

Willy Smith commented 16 August 2006 at 20:25

This is happening to me on two 4.6.5 sites. It started exhibiting this behavior all by itself; no changes were made to the sites. Strangely enough, I have another 4.6.5 site (new-physics.com) which does not do this. They are all hosted on SiteGround.

Contrib modules

dries commented 16 August 2006 at 20:54

- What contrib modules are you guys using?
- What Linux distribution are you guys using?

Time to start exchaning information about your setups!

Just happened to me as well

deadhobo commented 16 August 2006 at 21:51

I have a fairly recently 4.6.9 upgraded install that has been humming along well for several years. I woke up to the mis-organized front page (same as what has been discussed above). Below are my details:

Modules installed/activated:
basicevent, blog, comment, comment_closer, contact, contact_dir, countdown, event, feedback, filemanager, filter, forms, (UIE)forum, forward, gallery, glossary, gsitemap, help, htmlcorrector, logintoboggan, members, menu, node, page, paging, path, poll, poormanscron, porterstemmer, print, profile, quicktags, search, sidecontent, signup, statistics, story, superteaser, survey, system, tagadelic, taxonomy, taxonomy_access, upload, urlfilter, user, whatsrelated, xstatistics

Template:
Mollio

Server: (Copied from Cpannel)
Operating system Linux
Kernel version 2.6.17.6
Apache version 1.3.34 (Unix)
Machine Type i686
PHP version 4.4.2
MySQL version 4.1.21-standard

I really hope that a solution is found soon, this is a serious bug/flaw/problem.

I'm running 4.6.0. Within my

jase951 commented 16 August 2006 at 22:11

I'm running 4.6.0.

Within my modules, I have private modules but out of the modules that deadhobo has I have:

blog, comment, contact, filter, forum, gsitemap, help, menu, node, page, path, poll, print, profile, search, statistics, story, system, taxonomy, taxonomy_access, upload, urlfilter, user

Server:
Operating system Linux
Kernel version 2.6.17.6.dn2.p4
Apache version 1.3.36 (Unix)
Machine Type i686
PHP version 4.4.2
MySQL version 4.1.21-standard

I am to try a backup restore, to see if this helps me but I don't want this to happen again.

Is this a global issue? Time related (e.g. 15/08/06)?

just happened here within the past 48 hours

coloma commented 17 August 2006 at 00:04

drupal version 4.6.2

contrib modules:
dba v 1.21.2.1
ecommerce
image_filter v 1.16.2.1
inline v 1.2
node_privacy_byrole
taxonomy_access
webform v 1.48.2.10

Linux 2.6.16.17-grsec #1 SMP Mon May 22 04:30:56 PDT 2006 i686
PHP Version 4.4.2
MySQL Client API version 4.1.21
Apache/1.3.36 Server
Apache Release 10336100

Distribution?

sepeck commented 17 August 2006 at 00:33

The fact that this is hapening with different Drupal versions and the rest of your stats are remarkably similar seem to indicate that one of the distributions released an update for something....

Also.... please consider updating your Drupal versions to the latest point release soon... 4.6.0 and 4.6.2 have known security issue's

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide -|- Black Mountain}

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide}

To the best of my knowledge,

coloma commented 17 August 2006 at 05:27

To the best of my knowledge, no one has done any code updates on this site for several months. I'm not a real senior Drupal sort, but I can't imagine how a module being updated could cause a change if it wasn't installed? Am I missing something?

Added: I just verified that no files have changed on the server since March.

This bug showed up right after a blog entry was modified, and seems to only affect blogs. I had considered that a coincidence but now I'm not so sure.

Of the distro modules mentioned above, we are using:
blog, comment, contact, filter, forum, help, menu, node, page, path, profile, search, statistics, story, system, taxonomy, taxonomy_access, upload, user

same problem

andriko commented 17 August 2006 at 06:35

I'm tracked this to Mysql queries, but no solution.

site one(wrong order):

mysql> select distinct(c.nid), c.pid, c.cid, c.timestamp from comments c where c.status=0 order by c.timestamp desc limit 0,5 ;
+-----+-----+-----+------------+
| nid | pid | cid | timestamp  |
+-----+-----+-----+------------+
|  24 |   0 |  13 | 1149497103 |
|   9 |   0 |   2 | 1145602830 |
|   9 |   2 |   3 | 1145611954 |
|   8 |   0 |   4 | 1145950381 |
|  12 |   0 |   5 | 1146159331 |
+-----+-----+-----+------------+
5 rows in set (0.01 sec)

mysql> explain select distinct(c.nid), c.pid, c.cid, c.timestamp from comments c where c.status=0 order by c.timestamp desc limit 0,5 ;
+----+-------------+-------+------+---------------+------+---------+------+------+-------------+
| id | select_type | table | type | possible_keys | key  | key_len | ref  | rows | Extra       |
+----+-------------+-------+------+---------------+------+---------+------+------+-------------+
|  1 | SIMPLE      | c     | ALL  | NULL          | NULL |    NULL | NULL |  107 | Using where |
+----+-------------+-------+------+---------------+------+---------+------+------+-------------+
1 row in set (0.00 sec)

same data but different computer(my desktop, right order):

mysql> select distinct(c.nid), c.pid, c.cid, c.timestamp from comments c where c.status=0 order by c.timestamp desc limit 0,5 ;
+-----+-----+-----+------------+
| nid | pid | cid | timestamp  |
+-----+-----+-----+------------+
|  69 | 111 | 116 | 1155311297 |
|  74 |   0 | 115 | 1155112838 |
|  73 | 113 | 114 | 1155104707 |
|  73 |   0 | 113 | 1155067797 |
|  73 |   0 | 112 | 1155019022 |
+-----+-----+-----+------------+
5 rows in set (0.01 sec)

mysql> explain select distinct(c.nid), c.pid, c.cid, c.timestamp from comments c where c.status=0 order by c.timestamp desc limit 0,5 ;
+----+-------------+-------+------+---------------+------+---------+------+------+----------------------------------------------+
| id | select_type | table | type | possible_keys | key  | key_len | ref  | rows | Extra                                        |
+----+-------------+-------+------+---------------+------+---------+------+------+----------------------------------------------+
|  1 | SIMPLE      | c     | ALL  | NULL          | NULL |    NULL | NULL |  107 | Using where; Using temporary; Using filesort |
+----+-------------+-------+------+---------------+------+---------+------+------+----------------------------------------------+
1 row in set (0.01 sec)

Data on second PC exact copy from first site, same OS, apache2, MySQL, PHP, same drupal directory. I'm drop DB on first site and restore it, no joy :(

When looking for a cause to

sepeck commented 17 August 2006 at 17:45

When looking for a cause to an issue that occurs to a specific set of people 'suddenly' you have to look at comon configurations.

Here we have different Drupal versions. So we move on... What else is similier on the host systems and what may have recently changed.

One is the platform. Did a *nix distribution release an update recently. Did the host system do an auto update (many now do). Did a host provider recently upgrade their farm and others as well? If so, is it specific to a given php version.

It's not like there is a time code in Drupal that says 'one day change the display order of a site'. Could it be a bad query? Sure. But could it also be something that changed in a php/mysql code update and the query isn't as well written as it could be? More likely.

So... find out what is common and why it happened to several people with different Drupal distributions on different hosts at the same time. It's just the basic Troubleshooting stuff. You cannot look at Drupal itself (especially if you haven't changed your site for a while), you have to look at the environment that the affected sites are hosted on because Drupal relies on that to function. It's not happening to me and many others so those it is happening to need to help narrow down what / where something changed in their environment.

As to the version of Drupal people are using... Subscribe to the security newsletter. Some folks listed here are a bit behind the point release curve and some of the point releases have exploitable security vulnerabilities. That's a completely seperate thing from the display order issue but really should be scheduled soon.....

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide -|- Black Mountain}

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide}

CivicSpace 0.8.5 (built on 4.6.5?)

BlueNC commented 17 August 2006 at 11:49

PHP 4.4.2 on an Apache server.

Modules: aggregator, block, blog, blogapi, book, citizenspeak, comment, commentrss, contact, event, eventfinder, feedback, filter, flexinode, forms, forum, forward, gsitemap, image, location, mailhandler, massmailer, massmailer_rolelists, massmailertemplate, menu, nmoderation, node, notify, og, og_block, page, path, phplist, poll, private_message, profile, queue, scheduler, search, site_map, spam, statistics, survey, taxonomy, taxonomy_meny, taxonomy_xml, theme_editor, tracker, upload, user, watchdog, zadmin.

0.8.5 is built on 4.6.8

PAAHCweb commented 17 August 2006 at 16:32

0.8.5 is built on 4.6.8

When I log out of my site

BlueNC commented 17 August 2006 at 11:51

posts on teaser pages appear in the correct order (reverse chronological). This problem only seems to be a problem when users are logged in.

(posted again so that it is

jase951 commented 17 August 2006 at 12:32

(posted again so that it is at the bottom)

The problem appears only for current users and NOT new users.
This affects users with "administer nodes" access, meaning this is a core bug.

Wow

zwhalen commented 17 August 2006 at 16:17

It seems I get to join this party as well. Same problem, only appears for users with administer node permissions.

I have a few pages that, similar to the front page, list all content of a particular type using a pager_query(db_rewrite_sql()) type of syntax, and I found that the problem went away when I removed the db_rewrite_function. It seems as though the original ORDER BY ... DESC argument in my query is lost, and viewing the query list from the devel module bears out this observation.

I'm on 4.6.x and I think my host recently upgraded to PHP 4.4.3 and MySQL 4.1.10.

More here, but thanks to sepeck I'll follow this thread instead.

I'm in the party too! Just

Cromicon commented 17 August 2006 at 17:51

I'm in the party too! Just started happening today.
Same issue, administrators logging in have the node teasers on the front page listed in an incorrect order, other users are fine including anonymous. Using 4.6.9 so judging by the posts here it's a 4.6.x issue and as it's admin roles it does indeed look like core.

However!!!! On a post I made July 28th I was asked to list version details of server apps as I recommended Siteground: http://drupal.org/node/76053#comment-140953 For completeness, I am also with Siteground.

General server information as of 16/08/06 (08/16/06 for the USA contingent :-) )
Operating system Linux
Kernel version 2.6.14.2-grsec-grsec-test
Machine Type i686
Apache version 1.3.34 (Unix)
PERL version 5.8.7
PHP version 5.0.4
MySQL version 4.1.21-standard-log
cPanel Build 10.8.2-STABLE 120

I've looked at the only server side change that has occurred and the hosts have recently upgraded from MySQL version 4.1.19-standard-log to MySQL 4.1.21-standard-log. As it's query related I'm placing bets it's 4.1.21-standard-log bug or a hitherto unnoticed bug in a core query that came to light with this recent MySQL update although I notice one poster specifies MySQL 4.1.10 - zwhalen is it possible for you to check your version of MySQL for certain?

Oh, you're right.

zwhalen commented 17 August 2006 at 18:59

Sorry, I am also on 4.1.21 . Not sure where I saw 4.1.10, but phpinfo() definitely reports 4.1.21.

This happens after upgrade

onionweb commented 17 August 2006 at 18:05

This happens after upgrade to mySQL 4.1.21.

Earlier versions work fine.

Looked at MySQL.com

coloma commented 17 August 2006 at 18:52

Not sure whether this is relevant ... but here are release notes for 4.1.21:
http://dev.mysql.com/doc/refman/4.1/en/news-4-1-21.html

The only bug fix that seems related to "order by" is
http://bugs.mysql.com/bug.php?id=4981

And a check of their forum shows one thread that might be relevant?
http://forums.mysql.com/read.php?20,106815,106815

Hope this helps,
Donna

Yeah that looks like it,

Cromicon commented 17 August 2006 at 19:04

Yeah that looks like it, thanks Coloma.
http://forums.mysql.com/read.php?20,106815,106923#msg-106923

And to confirm, the hosts did the upgrade yesterday so it all ties in.

Now we need to sort it. Hands up those that are good with MySQL queries! Because I'm amazingly untalented. :-)

Issue logged

Cromicon commented 17 August 2006 at 20:06

Issue logged http://drupal.org/node/79229

I'm on MySQL

nig commented 17 August 2006 at 19:24

I'm on

MySQL v4.1.21-standard
PHP v5.1.4
Apache v1.3.36 (unix)
PERL v5.8.7

hope this helps the search

just discovered why the sudden rash of incidents

coloma commented 17 August 2006 at 22:45

According to my hosting provider:
"cPanel pushes out upgrades when it checks nightly for updates, and it looks as though [the MySQL 4.1.21 update] happened within the past two days"

So anyone on a cPanel host probably just got hit!

added: they just confirmed that the automatic update to 4.1.21 was exactly two days ago

Any drupal 4.6 or 4.7 site

onionweb commented 18 August 2006 at 04:40

Any drupal 4.6 or 4.7 site using an access control module such as node-privacy-by-role, simple-access, or organic-groups on a server running mySQL 4.1.21 has this issue.

Just replying to keep up

ryooki commented 18 August 2006 at 04:52

Just replying to keep up with the post.
___
www.liberalthinkers.org - a community for liberal viewpoints.

I have it too

Steve Viscido commented 18 August 2006 at 05:25

Yup I have this too.

So... for those of us who have no choice (my ISP upgraded their mySQL I assume... I sure didn't do anything), is there a solution for this? Perhaps a patch that can just re-reverse the order?

Steve

Workaround ?

bacatta commented 18 August 2006 at 11:42

If 4.7.x is also affected... is there any workaround at all ?

4.6.x user - http://baca2ta.free.fr/drupal/

I have two sites

gtoddv commented 18 August 2006 at 14:40

I have two sites running on the same server. One of them is exhibiting this behavior and the other isn't. The site that isn't having the problem works whether you are logged in or not. The other site(one with the probelm) is only accessible if you are logged in so I can't say if it matters. I will post more information as I get it. One thing I can say is the server is running MySQL 4.1.21.

gtoddv

All of my Drupal sites have

adamore commented 18 August 2006 at 15:49

All of my Drupal sites have reversed the order of posts. I've emailed my server, and they're calling it a global issue and saying I should upgrade to 4.7.3. Will this erase all of my posts/data? Upgrading?

And yes, the error is in MySQL 4.1.whatever.

Alice

Upgrading

Steve Viscido commented 18 August 2006 at 15:59

Upgrading to 4.7.3 should not erase your data (upgrading has never erased mine). However, as a precaution when upgrading you should always back up your data and your drupal directory, so if something goes wrong you can revert to the old system.

Steve

Upgrading won't fix the

onionweb commented 18 August 2006 at 16:25

Upgrading won't fix the problem. Deactivating any access control modules you have running will fix it. But then your private content will be public...

My version of drupal is too

adamore commented 18 August 2006 at 18:58

My version of drupal is too old, so the conversion to 4.7.3 is not working. Which access control modules are the problems? How can this be fixed?

There's an issue raised

Cromicon commented 18 August 2006 at 19:04

There's an issue raised further up in the thread, webchick is taking a look at things. It looks like any/all privacy/node access modules can be affected. She's requesting specific information on the issues thread if you'd like to help.

privacy_by_role

gtoddv commented 18 August 2006 at 18:17

I am running the privacy_by_role module which appears to be one of the potential culprits. I sure hope someone comes up with a fix. I am running a Statewide Intranet and this module if vital.

Anonymous or non-administrative roles do not appear to be affected by this issue. The only complaints I have recieved are from users with administrative rights.

Reversed Order

marrngtn commented 18 August 2006 at 19:33

Im running simple access w/Drupal 4.6 and definetely have the problem within the last 48 hours.

found fix for 4.5

emanherz commented 19 August 2006 at 13:56

Hi there in case anyone needs it, I'm still running 4.5 and having the error since yesterday. Using the info provided by others in the more recent versions I was able to find the line in 4.5 which seems to fix the problem.

It's in node.module around lines 1438.

Changed the following lines to

function node_page_default() {
$result = pager_query('SELECT n.nid, n.sticky, n.created FROM {node} n '. node_access_join_sql() .' WHERE n.promote = 1 AND n.status = 1 AND '. node_access_where_sql() .' ORDER BY n.sticky DESC, n.created DESC', variable_get('default_nodes_main', 10));

from
function node_page_default() {
$result = pager_query('SELECT DISTINCT (n.nid), n.sticky, n.created FROM {node} n '. node_access_join_sql() .' WHERE n.promote = 1 AND n.status = 1 AND '. node_access_where_sql() .' ORDER BY n.sticky DESC, n.created DESC', variable_get('default_nodes_main', 10));

in other words simply removed the word DISTINCT and brackets around the n.nid and it seems to have fixed the problem for me.

Eric

Another victim of the midnight compile

maui1 commented 18 August 2006 at 20:07

My host just did an upgrade and now I have the reverse order bug on at least one drupal site. Like others here the site absolutely requires the node access modules such as OG for their application, so any work around or patch would be greatly appreciated.

possible workaround

onionweb commented 18 August 2006 at 21:57

possible workaround here:

http://drupal.org/node/79217

needs testing

works for me

ryooki commented 19 August 2006 at 13:11

works for me without problems so far.
Drupal 4.6.? (forgot which one)

Seems to be okay now...maybe

Cromicon commented 19 August 2006 at 13:32

Seems to be okay now...maybe I had a weird caching issue but looks good so far.

Works for me on 4.6.9 with

deadhobo commented 19 August 2006 at 14:42

Works for me on 4.6.9 with taxonomy_access. Thanks!

Diffrent take - event date order

MattClare commented 18 August 2006 at 20:41

Does anyone know how to change the homepage to list nodes of the event type by date, not when they were created in 4.7?

I've looked at event_view and tried to find view filters -- dead ends (for me at least). I can sorth things how I want in the diffrent views, but I just can change the order in the main page.

So before I do something bad an hack base code, would someone mind pointing me towards the drupal way of doing this?

Many thanks in advance.

Oddly enough...

Steve Viscido commented 18 August 2006 at 21:10

Hm... Oddly enough... I was using 4.7.0. Yes I know it is time to update. I have found that it's best to do these one at a time and let them sit for a while and let the users at the site to make sure there are no "issues" as I update versions. So I went with 4.7.1 for now (then in a few days I'll do .2, then .3 a few days after that). Updating from 4.7.0 to .1 fixed this problem for me. I'm now seeing things correctly with the newest news item first.

So, for those having problems, even if upgrading to a newer version theoretically shouldn't fix this... try it. It very well might. I am not sure what voodoo went on to solve the problem for me with this update, of course... but heck, it can't hurt.

Just make sure you do a backup before trying it, of both your HTML directory and your SQL database.

Steve

weighing in belatedly

spyjournal commented 19 August 2006 at 06:15

i got two sites doing this also
it is only where node is set as the main page in admin|settings
so a work around is to use a category taxonomy link there instead
alternatively only have 1 or 2 posts on the main page and manually edit the dates so they flow in the right order.
alll other non main page posts - eg category links - work ok
we will watch and see on the issues for a work around re the mySLQ issue
The only other sire I have at the same level of druapl install is on a server that i control the MySQL upgrade on and it wont be getting upgraded until there is a fix

Same here

Clancy Ratliff commented 19 August 2006 at 13:58

I'm having the problem too: MySQL 4.1.21 and a Drupal 4.6.x installation. I have a low level of technical skill compared to the vast majority of you, and I'm hoping to get a solution I'll be able to implement from the admin menu, because I wouldn't be able to locate, much less fix, any code. I don't suppose there's anything I can do from admin --> access control or admin --> modules, is there? Thanks.

Here's the Fix for mySQL

onionweb commented 19 August 2006 at 15:31

Contact your webhosting provider and point him to this patch:

http://bugs.mysql.com/bug.php?id=21456

This is the result of a bug in mySQL 4.1.21 and beta5.

Thanks

spyjournal commented 20 August 2006 at 06:18

We will try that and let you know if it works
Cheers

Did it work?

jbeall commented 25 September 2006 at 14:34

Is this the solution?

provider performance re: patches

PAAHCweb commented 7 October 2006 at 16:36

How difficult / disruptive to the server is applying this patch?

My client uses CWIHosting. I requested the patch be applied on August 31st. They replied they would look into it. I asked again two weeks later. They said we're trying it on a test server - don't call us, we'll call you when we have decided if it can be applied. It's now 5 weeks later, and our posts are still out of order, with no word from the host.

Is applying a patch really that big a deal? What I read in the Drupal docs doesn't sound that complicated.

Thx,
D. Lynn

I have the same problem, Drupal 4.7.2

Steven Mansour commented 19 August 2006 at 16:46

Posts on the main page, on the "blog" overview page, and in any "recent" blocks I have appear in chronological order instead of reverse - only for admins who have "administer nodes" privies.

I'm using Site5 as a host - MySQL - 4.1.21-standard-log.

Here are my contributed modules:

adminrss
advuser
aggregator
block
blog
blogapi
book
comment
comment_info
commentrss
contact
dashboard
dba
event
eventrepeat
filter
flexinode
glossary
gmap
gmap_location
help
highlight
insert_block
live_discussions
location
logintoboggan
masquerade
menu
node
notify
***og***
og_basic
opensearch
page
path
pathauto
porterstemmer
print
profile
profileplus
quicktags
quote
search
search_config
simplenews
skypesupport
subscriptions
syndication
system
tagadelic
taxonomy
tracker
upload
user
userpoints
watchdog
webform
zeitgeist

This is also happening to me

Sam308 commented 26 August 2006 at 04:50

It's happening to me on two Drupal 4.6.8 websites

The oldest post are listed first "only" wnen I am logged in as the administator. Otherwise, it works correctly (new posts listed first) for both anonymous and regular logged in users.

Sam Raheb (Sam308)

Same problem

kevinwalsh commented 25 September 2006 at 14:05

For the record, it started happening after i installed captcha (probably not the cause), created a new access role, and uploaded some audio files (for the first time) that were tagged for visibility under only that new rolew, using TAC.
-kev
ps. i started a new thread without knowing about this one (i had first searched, among other thiings, for "sort order", one of the top 5 searches on drupal.org i believe) http://drupal.org/node/85210

heh

sepeck commented 25 September 2006 at 15:34

top 5 anonymous search terms
# cck (166)
# tinymce (152)
# calendar (143)
# forum (129)
# gallery (127)
# wiki (123)

top 5 for authenticated users
# cck (142)
# tinymce (65)
# views (63)
# acidfree (61)
# image (50)

:D There is a comment up there somewhere that mentions which MySQL patch fixes the issue.

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide -|- Black Mountain}

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide}

ooh

kevinwalsh commented 25 September 2006 at 15:49

looks like i got caught in a big fat lie there. ;-) top 10?
-kev

I just started having this

FatPitchFinancials commented 5 October 2006 at 05:45

I just started having this problem as well when "administer nodes" is activated for a role or the admin is logged in. I just upgraded 4.6.9 to see if this would help, but no change occurred. My cpanel version of MySQL is 4.1.20-standard-log and I'm using Bluehost. I am also using the taxonomy_access module, if that makes any difference.

Has anyone solved this problem? I didn't see any reports back yet. I did notice one possible solution in this thread but no confirmation that it worked.

The apparent fix is to wait

gtoddv commented 6 October 2006 at 16:38

The apparent fix is to wait for the 4.1.22 upgrade for MySQL (I am sure Bluehost is aware of the issue). I know that the problem does NOT exist in 4.7.3 if you are using node privacy byrole. I have not been able to fix it in any point version of 4.6 and have not seen a solution other than upgrading the database or get rid of any Node Access type modules.

Site5 has decided to move to MySQL 5.0 rather than wait for the 4.1.22 version.

anyone know what

kevinwalsh commented 6 October 2006 at 20:29

anyone know what implications the site5 upgrade to php 5 holds for us drupallers (in my case, 4.7.3?). i can't find anything in the documentation.

-kev

site5 upgrade to MySQL 5 postponed

kevinwalsh commented 13 October 2006 at 05:56

For those of you with Site5 awaiting the upgrade, it looks like the wait just got longer:
http://forums.site5.com/showthread.php?t=13077
-kev

As good a hosting company as

gtoddv commented 23 October 2006 at 14:27

As good a hosting company as site5 can be, this is not a huge surprise. Over promising has become an art form over there.

My solution is upgrading to 4.7.4. For whatever reason, the front page article list in the correct order in 4.7.3 and above, at least if the node access module you are using is 'node privacy by role'.

A similar problem only showing when Admin is logged in

oonumberoo commented 5 February 2008 at 21:55

Some of the above comments mention the problem showing when only Admin is logged in, but all is OK when Admin logs out.

I noticed that when Admin was logged in, some headings within a node were being corrupted, but were fine when Admin logged out and the node was viewed by the general public.

This was a good while ago, but the problem appeared to rest on the width of the window, a fraction too small for Admin, but OK for general view.

Might this have any bearing on the above? Probably not.

homepage started listing nodes in wrong order

Comments

New forum topics