Page 1 of 1

Update serendipity_plugin_adduser failed

Posted: Wed Apr 28, 2010 9:42 am
by search1
I have a CMS with serendipity and digital certificate. After the serendipity update from 1.4.1 to 1.5.2 the old serendipity_plugin_adduser (2.29) failed: The startpage shows a link to https://www.domain.tld/index.php?serend ... e]=adduser (this works: the correct form comes), a mail is sent to the right blog-Email to allow it (this works) , the allowing-link works, but has a strange look (:443) (https://www.domain.tld:443/index.php?r= ... de#adduser), after allowing a mail is sent to the new user-e-Mail (this works), the new user can activate the new account (this works, the account is created, but the activation-link has a strange look (:443) (https://www.domain.tld:443/index.php?se ... de#adduser), but then the new user can´t login, because the password doesn´t work.
Then I updated the serendipity_plugin_adduser in the serendipity-backend with Spartacus to 2.34 and then nothing worked: The backend showed a right update to 2.34. In serendipity\plugins the serendipity_plugin_adduser is updated, but there is also a new emty file folder serendipity_event_adduser. If a not registrated user takes the link in the startpage to registrate, in the adressline of the browser is showed: https://www.domain.tld/index.php?serend ... e]=adduser, but the startpage is still there.
What can I do?

Re: Update serendipity_plugin_adduser failed

Posted: Wed Apr 28, 2010 12:00 pm
by yellowled
I seem to remember the serendipity_event_adduser.php being patched in this particular project's setting. This now probably has been overwritten by the update.

[quoteIf a not registrated user takes the link in the startpage to registrate, in the adressline of the browser is showed: https://www.domain.tld/index.php?serend ... e]=adduser, but the startpage is still there.][/quote]
Knowing the project's URL, I checked this out. Works for me - the registration link takes me to the registration page.

YL

Re: Update serendipity_plugin_adduser failed

Posted: Wed Apr 28, 2010 12:51 pm
by search1
yes, the registration page works, because I use the former version of adduser with the problems, I wrote.

Re: Update serendipity_plugin_adduser failed

Posted: Wed Apr 28, 2010 3:21 pm
by garvinhicking
Hi!

When you use https:// links to access your backend you must make sure that the configuration links you enter anywhere in the config use http:// instead of https://

(:443 is https port)

Regards,
Garvin

Re: Update serendipity_plugin_adduser failed

Posted: Wed Apr 28, 2010 5:59 pm
by search1
Thanks; thit is the reason!
I use a .htaccess to switch all adresses in the browser zu https, so it seams difficult to use http? I wrote in the serendipity\plugins\serendipity_plugin_adduser\common.inc.php every time instead of $serendipity['baseURL']: 'http:/www.domain.tld/', also in the serendipity\plugins\serendipity_plugin_adduser\serendipity_event_adduser.php. The result: after the registration is showed the startpage, not the confirmation-site.
If I use instead of $serendipity['baseURL']: 'https:/www.domain.tld/', everything is the same as with $serendipity['baseURL']. What can I do?

Re: Update serendipity_plugin_adduser failed

Posted: Wed Apr 28, 2010 10:34 pm
by garvinhicking
Hi!

When you have the s9y option "autodetect http-hostname" enabled and you login on a https domain, s9y changes that variable for your request to https, and thus it might enter it into any config field.

Do you use http:// or https:// when you access your frontend? Do you want your visitors to use https, or only you?

Regards,
Garvin

Re: Update serendipity_plugin_adduser failed

Posted: Wed Apr 28, 2010 11:16 pm
by search1
Hi Garvin,

thanks for your answers!
I use always https:// : For my frontend-access and also the visitors use https://
The change in the s9y option "autodetect http-hostname" to enabled makes no different...

But this problem isn´t too big, because my CMS becomes soon a new account-generation ;-)