WebLoginPE (1.3.0): Advanced WebUser Management and Extended Profiling.

Now I tested WebLoginPE on two new fresh installations on two different servers, but with little success.

For testing purposes it should be enough to just call [!WebLoginPE!] with no other parameters, is that correct?

When doing that the login form displays, but nothing happends when pressing the buttons in FF2. Well, one out of 100 times it displays the lost password part... If I use IE7 it works fine, and I also get the error messages.

Then I’ve also created a test page for registering, and there I have a call like this:



It displays the form, but when entering bad data or no data I get no error message, not in FF and not in IE7.

What more do I have to do to set up this little test to be working? Should I enter placeholder for the error messages manually ( [+wlpe.message+] )?

Quote from: Uncle68 at Sep 02, 2007, 07:23 PM

Now I tested WebLoginPE on two new fresh installations on two different servers, but with little success.

For testing purposes it should be enough to just call [!WebLoginPE!] with no other parameters, is that correct?

When doing that the login form displays, but nothing happends when pressing the buttons in FF2. Well, one out of 100 times it displays the lost password part... If I use IE7 it works fine, and I also get the error messages.

Then I’ve also created a test page for registering, and there I have a call like this:

[!WebLoginPE? &type=`register` &regRequired=`email,username,fullname,password,tos` &regType=`instant`!]

It displays the form, but when entering bad data or no data I get no error message, not in FF and not in IE7.

What more do I have to do to set up this little test to be working? Should I enter placeholder for the error messages manually ( [+wlpe.message+] )?

Wow Uncle68. Now I am really confused. I cannot, for the life of me, recreate these errors. You do not need to put the placeholder anywhere because it is already in all the default templates.

Both the snippet calls above are exactly correct for proper function. Why don’t you run your server stats by me.
I have tested this on both Mac and Linux using PHP 4.4.6 and PHP 5.2.1

Anyone else experiencing this?

I run PHP Version 5.2.3 one one server and 5.2.4RC2 on the other, I have several other MODx installations that work fine on these servers.

I must go to sleep now, but tomorrow or on tuesday I can pm you access to the server and manager so you can check it out for your self.

Now I need my 5 hours sleep

I had a very perplexing experience lately where my pages acted as if the were cached no matter what I did. Only pressing F5 to refresh the page from the browser loaded the updated version of the page. It turns out that this host is running mod_expires, and it was adding its own headers to MODx’s and effectively making every page cached.

From Uncle68’s description it sounds as if something similar might be going on, so maybe this post on how I resolved it will help.

Thanks for making WebLoginPE work with PHP 4, Scotty! We have about 20 sites on a PHP 4-only host, and I was very sad when I originally read that it only worked with PHP 5. If I can only get them to update their MySQL I’ll be satisfied...

ZAP, yes, both my servers have mod_expires enabled.

Do you perhaps have the exact syntax for turning it off in .htaccess? Otherwise I can look around...

Could be worth testing turning it off to see if this fixes the problems I have.

EDIT: How strange! Today the buttons are working as they should, but only on one of the two installations on one of my servers! This is confusing! I’ll test some more later.

EDIT2: If I turn off the page caching on the documents where I have a call to WLPE it works as it should on all three installations on the two servers! And yes, I did call WLPE uncached... This sure seems to be a chache problem.

@Uncle68: Adding "ExpiresActive Off" to your .htaccess file should turn mod_expires off and at least eliminate that as a variable. Check the thread I linked to above for more on how I went through something similar and pulled my hair out trying to understand why things weren’t caching correctly. mod_expires adds headers that your browser will obey, so the caching is happening locally in your browser and not on the server (which explains why it acts so strangely).

I know that there are some practical uses for mod_expires, so if you don’t want to completely turn it off check the link in the other thread for more specific info on how to set it up properly.

Then again, it might not be mod_expires I suppose... I know that I’ve found that MODx placeholders can be a little bit unpredictable. I find that if I set them to something (usually a space) instead of just initializing them as empty that they don’t recycle old values, but I haven’t investigated why that might be at all.

And of course if your placeholders are outside of your snippet call (not returned in a template by the snippet itself), then you have to make the document uncached for them to update (or you can add simple uncached snippets that just return the placeholders in their respective places).

I’m going to have to try this WebLoginPE thing our myself soon; it looks very slick.

I’ve been happily running v1.1.1 on the works intranet and the forever login is brill.. as well as some of the other features but I’m looking forward to testing the new one

Thanks Scotty

@Uncle68:
Interesting. I never have caching "On" on my pages. Thanks for finding and reporting this. I will see if there is something that I can do to correct it, otherwise it is nice to at least know how to remedy it.

@Zap:
Boy am I glad you are reading this forum. I would have never known that.

@BBloke:
It is cool to hear about how people are using it. Glad you like it. I too am excited about what is coming next in WebLoginPE.

-sD-
Dr. Scotty Delicious, Scientist DFPA.

Super! Thanks Scotty for PHP 4 support in new version, its realy cool for me.

Just to check --- the "manage" addition for special Admin. only profile fields + user list sorting would likely be in the next version of WLPE, right?

I needed to restart my web user program anyway, so once those two fields are done, I’ll basically be able to move from PPP to WLPE with ease (since all of the functions will be implemented by that point).

I’m not trying to rush you or anything like that --- I’m just wondering when in the "roadmap" for WLPE that they’ll be implemented, so I can know when I’ll be needing to start converting over to WLPE.