Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#793 2011-06-18 21:08:08
Re: ign_password_protect
authentification not working on new release : txp 4.4.1 (i use alternate database)
I use ign version 6.1 (from igner github) and also tried manfre version but both failed!
The connexion work but when i click a link i got message “There was a problem logging in.”
Last edited by Dragondz (2011-06-19 11:18:20)
Offline
#794 2011-06-20 18:49:20
- igner
- Plugin Author
- Registered: 2004-06-03
- Posts: 337
Re: ign_password_protect
well – just confirmed that there remain some issues with the alternate DB. if I can carve some time, I’ll try to track down the source of the issue, but make no guarantees on the timing.
And then my dog ate my badger, and the love was lost.
Offline
#795 2011-06-20 18:57:49
Re: ign_password_protect
Just to clarify, will Manfre’s version work with TXP 4.4.1 for sites that use Textpattern’s user table?
Offline
#796 2011-06-20 19:18:30
- igner
- Plugin Author
- Registered: 2004-06-03
- Posts: 337
Re: ign_password_protect
johnstephens wrote:
Just to clarify, will Manfre’s version work with TXP 4.4.1 for sites that use Textpattern’s user table?
you’ll probably want to grab 0.6.1 from github
Manfre’s version will mostly work, but admin-side users can potentially get a visit from the bouncer…
And then my dog ate my badger, and the love was lost.
Offline
#797 2011-06-20 19:43:56
Re: ign_password_protect
Thank you, Jeremy!
I’m guessing that 0.6.1 is based on Manfre’s version, so upgrading shouldn’t be any trouble. Is that a sound supposition?
Offline
#798 2011-06-20 20:40:41
- igner
- Plugin Author
- Registered: 2004-06-03
- Posts: 337
Re: ign_password_protect
yup – i merged Manfre’s changes into the repo before doing the update.
And then my dog ate my badger, and the love was lost.
Offline
#799 2011-06-20 20:50:21
Re: ign_password_protect
Thanks again, Jeremy!
Offline
#800 2011-06-21 08:44:36
Re: ign_password_protect
I confirm that ign_password_protect works using txp table (not tested all features), but something boring me is that when i am logged on admin side, i am also logged on public side, and when i try to logout from public side, i am also logged out from admin side!!
@ Jeremy: thanks to take care about that, and time is time, do what you can.
Cheers
Offline
#801 2011-06-21 13:41:05
Re: ign_password_protect
Dragondz wrote:
when i am logged on admin side, i am also logged on public side, and when i try to logout from public side, i am also logged out from admin side!!
For me, this is a feature, not a bug.
Offline
#802 2011-06-21 15:13:39
Re: ign_password_protect
johnstephens a écrit:
For me, this is a feature, not a bug.
Yes, but when i used a separate user table that not occured, in my case i separate completely admin side and public side that why that feature is not suitable.
Offline
#803 2011-06-29 04:40:09
- kevinpotts
- Member
- From: Ghost Coast
- Registered: 2004-12-07
- Posts: 370
Re: ign_password_protect
igner wrote:
johnstephens wrote:
Just to clarify, will Manfre’s version work with TXP 4.4.1 for sites that use Textpattern’s user table?
you’ll probably want to grab 0.6.1 from github
Manfre’s version will mostly work, but admin-side users can potentially get a visit from the bouncer…
Is this available as a true .txt update? I only ask because when I edit the plugin’s source with this new PHP, all I get are warnings across Textpattern that look like this:
I'm sorry. I'm afraid I can't do that. I think page page_save is no safe operation at this time.I tried logging as myself (the Publisher) and as a test account and got the same results. Plugin works on the public side, but breaks the admin side. Thoughts? (Running 4.4.1)
Kevin
(graphicpush)
Offline
#804 2011-06-29 20:32:17
- igner
- Plugin Author
- Registered: 2004-06-03
- Posts: 337
Re: ign_password_protect
kevinpotts wrote:
igner wrote:
Is this available as a true .txt update? I only ask because when I edit the plugin’s source with this new PHP, all I get are warnings across Textpattern that look like this:
I'm sorry. I'm afraid I can't do that. I think page page_save is no safe operation at this time.I tried logging as myself (the Publisher) and as a test account and got the same results. Plugin works on the public side, but breaks the admin side. Thoughts? (Running 4.4.1)
Hmm – that doesn’t sound right…but that’s the very issue the changes are intended to address. A compiled version is available here
Let me know if this solves the issue.
And then my dog ate my badger, and the love was lost.
Offline