After upgradeing from 4.4 to 4.5 and some time (1/2 a hour?) I get 20 empty listings with the head "Updated more than 305802 hours ago:"
Any way to reset the counter? TIA
After upgradeing from 4.4 to 4.5 and some time (1/2 a hour?) I get 20 empty listings with the head "Updated more than 305802 hours ago:"
Any way to reset the counter? TIA
Comments
Comment #1
bertboerland commentedafter about one hour everything was fine again.
Comment #2
Bèr Kessels commentedany idea what might have caused this?
Comment #3
bertboerland commentedno, I was bizzy wit implenting all the modules and configuring them. I am sure that cron has run before the rror resulting in a good weblink block. I do have my host synchronised with an ntp server so exterme time shift are not an option. I quess one variable went over the hill.
Comment #4
bertboerland commentedFor anonymous users (see htpp://willy.boerland.com/myblog) the weblink is still empty. Registerd users have a normal weblink (try to login with your drupal id in case you want to check this)
Comment #5
ericatkins commentedMy account. I recently posted to the forums (http://drupal.org/node/13289)
I recently started getting this bug on 2 sites:
When users without the permission to "administer nodes" visits http://cookedgamers.net, my weblinks monitor says:
Monitored weblinks
Updated more than 305856 hours ago:
*
*
*
*
*
*
*
*
*
*
etc.
-------------
So basically, everyone who is not an admin on the site can not use the Monitored weblinks block. When users are given permission to "administer nodes" the Monitored weblinks appear as normal.
This case has happened recently on 2 sites. Both sites were running idential modules. On both sites, I deactivied the node_privacy_byrole module. I suspect that node_privacy_byrole is causing the error, however, this may not be the case as I did more tinkering with the sites before I realized the error.
Has anyone ran into this problem before?
Can anyone offer some direction as this module is an important module to my sites.
Comment #6
Bèr Kessels commentedjust to be able to exclude certain problems:
"Do you have Cache enabled? "
Admins do not see cached pages, while ano users do!
Bèr
Comment #7
bertboerland commentedI disabled caching (was enabled) and still the pages for non admin have the weird time offset and an empty list.
Comment #8
ericatkins commentedComment #9
junyor commentedFrom the sounds of it, something is failing in weblink_monitor_list(), causing the weblink nodes not to be loaded. The numbers people are seeing is simply floor(time() / 3600). From a look at the code, I'd say the most likely culprit is the node_load() function. I have no idea what the problem is or how to fix it, though.
And, for the record, I'm seeing this problem too. :(
Comment #10
hafif uyku commentedIn case of an emergancy: this problem goes away if you remove the ". node_access_join_sql() ." and AND ". node_access_where_sql()." from the weblink_monitor_list() query.
Comment #11
bertboerland commentedthanks. this IS the line that is causing the problem looking by the time minus 604800 part. however deleting these two statements dindt do it for me (now both anonymous and registerd users have an empty list :-(
here the diff to make sure I did the right thing:
diff weblink.module weblink.module.org
612c612
< $result = db_query_range("SELECT * FROM {weblink} n WHERE change_stamp > ". (time() - 604800) ." AND ORDER BY change_stamp DESC", 0, $limit);
---
> $result = db_query_range("SELECT * FROM {weblink} n ". node_access_join_sql() ." WHERE change_stamp > ". (time() - 604800) ." AND ". node_access_where_sql()." ORDER BY change_stamp DESC", 0, $limit);
The line above this part makes the users global so I dont get why anonymous users are treated in another way than logged in users? Any more hints are welcome.
--
groets,
bertb
Comment #12
Bèr Kessels commentedI have an idea, but no time to test or proof it.
Cron is ran as anonymous, but uses some functions. Thus the functions called by cron, should allos anonymous to "do stuff".
The access_sql will disallow cron to do his job.
\
Bèr
Comment #13
m_freeman2004 commentedHi,
I'm getting the same problem under 4.5.0. Any ideas yet?
Marcus.
Comment #14
(not verified) commentedThis was really close.
Still, no answer to this problem though.
Comment #15
bertboerland commentedSo hereby I offer 10 Euro to the person who solves this problem. Might be a problem when you are from outside the EU. If you dont want the 10 E I will double it and donate it to a charity cause (including OSS projects like drupal itself) picked by you.
So you want to help me and others out here, and make a buck or donate two, try to solve this one.
Comment #16
James Addison commentedHas their been any input on this outside of this 'issue' thread? Has anyone expressed an interest or knowledge that would help in fixing it? I took a quick look last night, but I'm not familiar enough with the code. I guess I'll keep trying, though.
Comment #17
junyor commentedWell, I think it's pretty clear that it's a permission problem. If you look at the last several comments, there's a good bit of information there about work-arounds and analyses.
Comment #18
ericatkins commentedI really wish there was a solution for this, also. A lot of people were visiting my sites just to see when other sites were updated.
I have dug around in the code and had a partial solution like some of the others in this thread.
I'll throw in $20 via paypal to anyone that gets this problem solved.
Comment #19
bertboerland commentedWhich sums up to 30 euro for just a bit of debugging ;-) any takers?
Comment #20
ericatkins commentedI don't think many people view this page. :(
Comment #21
Bèr Kessels commentedI do,
But unfortunately I am being held on other tasks ATM. But most impoartantly: we are revising the complete links system. So fixing this makes littkle sense, since a few weeks after the 4.6 the new system will see daylight. Hence the old weblinks will probably not be updated for CVS/4.6.
Bèr
Comment #22
James Addison commentedI'm hoping that the old weblinks will migrate over to the 'new' model during the upgrade process - is it fair to assume that, Bèr?
Thanks,
James Addison
http://www.pjsoft.ca
Comment #23
Bèr Kessels commentedNo, not really.
Most functionality will be replaced, but certainly not all. For example the directory system will surely be removed.
Comment #24
James Addison commentedActually, I was referring to the content of the weblinks - the URLs, descriptions, etc. I have confidence that the necessary functionality will be retained, in a new form that makes sense. I would just hate for users to lose their weblink information.
Thanks,
James Addison
http://www.pjsoft.ca
Comment #25
Bèr Kessels commentedYes, I will not release my new weblinks systems, untill I have proper update scripts/systems or backwards compatibility systems in place.
Comment #26
bertboerland commentedBer, any idea when / if you will release a new weblink version for 4.6?
Comment #27
Bèr Kessels commentedI was promised to get some patcheslast monday, but I guess somewhere before coming weekend we will be able o do some mayor upgrades.
Comment #28
Bèr Kessels commentedAll features etc are blocked for 4.7. please move over to the links project.