Hi, I'm trying to run Vote Up/Down with Drupal 5, and the weirdest thing's happening. Yesterday I set up a fresh 5 installation, switched on Vote up/down, Voting API, actions, CRE, Links, and the Path module. Everything was working great. I switched on several other modules, including pathauto and poormanscron and everything was still working great. A few hours later, I came back and the titles of all my storylinks (which are supposed to link to the URL's they're given) were now pointing to the nodes themselves exclusively. I messed with my settings trying to fix whatever had happened....no change.
I uninstalled every module, one by one and checked the links after each removal...no change. I was sure pathauto had done it, but when I uninstalled it, the links were still not showing what they were supposed to. In disgust, I deleted the whole installation. Today, I started over....set it up...everything was working...this time I turned on my other modules one by one, testing the title links after each activation...no problems...I turned on pathauto, cleared the default path structure field and filled in stuff for all the others, leaving the Storylink path field empty (I'd read that this would leave the story links alone). Everything was working great.....4 hours later, Iog in again...and the links are pointing to the nodes all over again!!!!
What the heck is happening here? How do I reverse it? Please help! This is really disappointing.
Comments
Comment #1
frjo commentedYou have forgotten to add the node-storylink.tpl.php and template.php to your theme. See the included INSTALL.txt for more information.
Comment #2
frjo commentedComment #3
bflora commentedNope. I Definitely did that. I even followed the directions for how to merge the template.php from the module and the template.php from my theme that were posted here in the support forum.
As I said....both times, everything would be working just fine. (The only way it would be working fine would be if I'd moved those files where they needed to be). I guess I'm wondering if pathauto, jtools or something else could have triggered this? Or maybe a cron job from poormanscron (which would explain things breaking AFTER they were working)? It's not just the theme files, that's obvious stuff. I followed your directions in every way.....and this happened.
You can see what's happened at bradsguide.org. Here: http://bradsguide.org/storylink/top/week
Look at the URLs for those links. It's the weirdest things. It's like the node.storylink.tpl.php setting are being "overtaken" by something else and broken. (You'll notice two XX's after each link, I put them there to prove I've got the node.storylink.tpl.php file in place...)
How do we fix this? Thanks!
Comment #4
totaldrupal commentedI have this same problem. Links working then stop.
Comment #5
frjo commentedWith proper use of node-storylink.tpl.php and template.php I have nerver seen this issue. My guess is that you have some trouble with your theme.
Comment #6
thinguy commentedI'm seeing the same thing in a fresh 5.3 install using Garland.
Anyone found out why?
Comment #7
awong commentedIt is working for me. And i also install the pathauto module, but the storylink still working. Can you give more detail on this issues? or like step by step that how to reproduce the error? thanks
Comment #8
bflora commentedCould it be a caching issue?
Also, I'm not Drupal wiz, but I know my HTML/CSS cold. And I know that as long as those don't change, then you can't blame the changing URL's on them. The fact that it works at first means that the template's are correct (in theory!). That's why I'm so confused by this. What exactly is changing that causes the URL's to change? So strange. Are there any automated processes that happen every hour that could be "resetting" the URL's in the story links?
And after these changes happen, I've tried everything to change them back, disabling every module except the core one's required by Vote-Up/Down...and still nothing.
It's baffling.
I'm going to take another stab at it again and will post what happens in this thread.
Comment #9
marvil07 commentedPlease take a look to the update on the project page, now
5.xis not-really-maintained.If you think your question is still applicably to the last recommended version(
6.x-2.x) please move the version accordingly and reopen it.