Upgrade to 6.8/6.9 breaks all taxonomy listings
Greetings, I *do* know that is list is for development, not for support, sorry. But I have already tried two times, both on the support list and in the drupal forums, to get some answer, any answer to something which probably requires top drupal expertise to solve. I got a serious problem which I explained in detail here: http://drupal.org/node/356394 http://drupal.org/node/358739 (for the record, I just upgraded to 6.9 and nothing changed). I'm a bit worried that in one week there was no reaction whatever to something like this. Didn't I provide enough information? How can I find out what went wrong and how to fix it? I have no problem to study documentation or do command line work myself. I also have ssh and phpmyadmin access to that server, but honestly I need some pointer to get started in the right direction (assuming this is a problem in my site and not a bug in Drupal). What's the problem? Why did those listing disappear? Please let me know and don't hesitate to ask for more info, tests to run on the server, whatever. TIA, Marco -- Help *everybody* love Free Standards and Software: http://digifreedom.net
If you find a bug, in 99% of cases there'll already be a report on the issue queue, like this one http://drupal.org/node/345080 You can search the issue queue using http://drupal.org/project/issues/search/drupal - only a very small proportion of people working on core look at the forums, which IMO should never be used to post bug reports since there's no tracking whatsoever and because they're completely outside the normal core and contrib workflow. If you could run the upgrade again and post any error messages to that issue, it might help tracking it down. Nat On Fri, Jan 16, 2009 at 9:05 AM, M. Fioretti <mfioretti@nexaima.net> wrote:
Greetings,
I *do* know that is list is for development, not for support, sorry. But I have already tried two times, both on the support list and in the drupal forums, to get some answer, any answer to something which probably requires top drupal expertise to solve. I got a serious problem which I explained in detail here:
http://drupal.org/node/356394 http://drupal.org/node/358739
(for the record, I just upgraded to 6.9 and nothing changed).
I'm a bit worried that in one week there was no reaction whatever to something like this. Didn't I provide enough information? How can I find out what went wrong and how to fix it? I have no problem to study documentation or do command line work myself. I also have ssh and phpmyadmin access to that server, but honestly I need some pointer to get started in the right direction (assuming this is a problem in my site and not a bug in Drupal).
What's the problem? Why did those listing disappear? Please let me know and don't hesitate to ask for more info, tests to run on the server, whatever.
TIA, Marco
-- Help *everybody* love Free Standards and Software: http://digifreedom.net
Problem solved on http://drupal.org/node/358739 ----- Original Message ----- From: "Nathaniel Catchpole" <catch56@googlemail.com> To: <development@drupal.org>; <mfioretti@nexaima.net> Sent: Friday, January 16, 2009 11:03 AM Subject: Re: [development] Upgrade to 6.8/6.9 breaks all taxonomy listings If you find a bug, in 99% of cases there'll already be a report on the issue queue, like this one http://drupal.org/node/345080 You can search the issue queue using http://drupal.org/project/issues/search/drupal - only a very small proportion of people working on core look at the forums, which IMO should never be used to post bug reports since there's no tracking whatsoever and because they're completely outside the normal core and contrib workflow. If you could run the upgrade again and post any error messages to that issue, it might help tracking it down. Nat On Fri, Jan 16, 2009 at 9:05 AM, M. Fioretti <mfioretti@nexaima.net<mailto:mfioretti@nexaima.net>> wrote: Greetings, I *do* know that is list is for development, not for support, sorry. But I have already tried two times, both on the support list and in the drupal forums, to get some answer, any answer to something which probably requires top drupal expertise to solve. I got a serious problem which I explained in detail here: http://drupal.org/node/356394 http://drupal.org/node/358739 (for the record, I just upgraded to 6.9 and nothing changed). I'm a bit worried that in one week there was no reaction whatever to something like this. Didn't I provide enough information? How can I find out what went wrong and how to fix it? I have no problem to study documentation or do command line work myself. I also have ssh and phpmyadmin access to that server, but honestly I need some pointer to get started in the right direction (assuming this is a problem in my site and not a bug in Drupal). What's the problem? Why did those listing disappear? Please let me know and don't hesitate to ask for more info, tests to run on the server, whatever. TIA, Marco -- Help *everybody* love Free Standards and Software: http://digifreedom.net
On Fri, January 16, 2009 11:12 am, FGM wrote:
Problem solved on http://drupal.org/node/358739
er, no, with all respect it isn't is it now? See my answer at 10:25 on that same page . Your answer is surely useful for other developers to diagnose the issue, but how is a website visitor supposed to know that if he wants to see what Drupal says it's at http://storiafse.net/taxonomy/term/67, he should manually add a /1 to the URL? Please let me know if you need more info from me (including running tests) and if and how it's possible to make that term_node table work again, even by working manually at the mysql prompt. Thanks, Marco -- Help *everybody* love Free Standards and Software: http://digifreedom.net
On Fri, January 16, 2009 11:03 am, Nathaniel Catchpole wrote: Nathaniel, thanks a lot for the prompt answer. Now:
If you find a bug, in 99% of cases there'll already be a report on the issue queue, like this one http://drupal.org/node/345080
I **had** tried several searches before asking for help. I know how to find for help, provide as much info as possible etc, but this time, for some reason, simply missed that page, thanks. However: 1) Yes, the symptoms are the same I have, so it must be the same bug 2) Like the others, I have not seen any related error/warning during the 5.5->6.8 upgrade, otherwise I'd have posted them one week ago 3) Please see again http://drupal.org/node/358739 where interesting comments appeared a few minutes ago 4) wrt the bug tracker, the only difference in my case, is that I also upgraded from 6.8 to 6.9. Also, my (6.9) term_node table is not empty. I don't know if and how this and the comments in point 3 above are all related. is it possible to rebuild the term_node table so that it works with sane URLs? I have no problem to work at the mysql prompt, but I need to know what to do. What now? If you need to look at the exact content of the table, just ask. Thanks! Marco -- Help *everybody* love Free Standards and Software: http://digifreedom.net
participants (3)
-
FGM -
M. Fioretti -
Nathaniel Catchpole