Closed (fixed)
Project:
Premium
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Jan 2007 at 20:00 UTC
Updated:
2 Aug 2008 at 15:32 UTC
Jump to comment: Most recent file
Comments
Comment #1
allie mickaIt doesn't work :)
But I'm fixing it, as part of #68547 , and thus marking it as a duplicate.
thanks!
Comment #2
Dabitch commentedThere's a patch in #68547 and it's closed marked as "fixed" from way back in June. I've only recently (that is, long after June) upgraded my premium and drupal to 5.3 and still have the issue with premium not being able to do the advertised 'switch to premium after X time' thing, which I want.
Is there a specific premium module I should be using to make this work? Should I be patching the 5.x-1.x-dev one that I have? Is this issue fixed or only the other part of it? Is it my site that's being weird (then, maybe I can help?)
Comment #3
Dabitch commentedIn other words, I need more info - hope I'm doing the right thing here I've never re-opened an issue before.
Comment #4
Dabitch commentedSorry, I've helped myself. this patch:
worked fine for me when cut and pasted into premium 5.x.1-dev. Cheers.
Comment #5
Dabitch commented(edited triple-posted comment away)
Comment #6
Dabitch commented(edited triple-posted comment away)
Comment #7
Dabitch commenteduhm... I don't understand why my comments won't show up though. edit aha, must have been some cache issues as I didn't see them posted until now, hours later.
Also, didn't quite work as expected (that patch above) - now all of my nodes were accessable by non-premium users, no matter how ancient the post or how often I set the settings to 5-4-3-2-1 days. I went back to the original module instead.
Back to square one.
Comment #8
jerdavisI believe this should be fixed in the current 5.x build. If you're still having issues, please download a new tarball and replace your existing module. Then make sure that premium.module looks something like this starting around line 44:
If you still run into issues, please re-open and let us know.
Comment #9
jerdavisActually, I took a deeper look at this and did some testing - and it was in fact broken. I've created a patch, and have verified it as working now on my local system. This patch is a cvs diff against HEAD.
Comment #10
theorichel commentedI have applied the last patch in this thread (post #9). Before I did, setting a document to Premium had no effect at all. The checkbox-setting was gone the next time I opened the document. And all content was available.
Now it remembers the setting, but it still has no effect: the document is still entirely accessible to anyone, only it has a line printed at the bottom saying that this is premium content.
Update: I now know what the above patch has done: added a default check in the 'Set as premium-content' box. In the situation before one couldnt add it. Now I cannot remove it anymore. The check restores itself (though all pages are accessible).
Comment #11
jerdavisRebuilt this patch against the current HEAD as some cleanup had invalidated the old patch. This new patch also fixes the issue noted in http://drupal.org/node/282682
Comment #12
allie mickaCommitted. Thanks!
Comment #13
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.