PacketFence - BTS - PacketFence | |||||||||||||||
View Issue Details | |||||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||||
0001608 | PacketFence | guests | public | 2012-11-13 11:34 | 2012-11-13 12:26 | ||||||||||
Reporter | jbehrend | ||||||||||||||
Assigned To | dwuelfrath | ||||||||||||||
Priority | normal | Severity | major | Reproducibility | always | ||||||||||
Status | closed | Resolution | duplicate | ||||||||||||
Platform | OS | OS Version | |||||||||||||
Product Version | 3.6.0 | ||||||||||||||
Target Version | Fixed in Version | 3.6.1 | |||||||||||||
fixed in git revision | |||||||||||||||
fixed in mtn revision | |||||||||||||||
Summary | 0001608: Wrong email activation Link | ||||||||||||||
Description | When a sponsor gets his email with the activation link, I encountered a double backslash: In order to activate access we need you to click on the following link: https://packetfence.mpifr-bonn.mpg.de/activate/email//1234b4b8f364b29379372d5c02016f70 [^] which leads to the wrong rewrite rule to the captive portal. I think the last backslash here is too much: ./pf/web/constants.pm:Readonly::Scalar our $URL_EMAIL_ACTIVATION => '/activate/email/'; This leads to additional backslash problems in the rewrite rule in bug 0001607 | ||||||||||||||
Steps To Reproduce | |||||||||||||||
Additional Information | |||||||||||||||
Tags | No tags attached. | ||||||||||||||
Relationships |
| ||||||||||||||
Attached Files | |||||||||||||||
Issue History | |||||||||||||||
Date Modified | Username | Field | Change | ||||||||||||
2012-11-13 11:34 | jbehrend | New Issue | |||||||||||||
2012-11-13 12:26 | dwuelfrath | Assigned To | => dwuelfrath | ||||||||||||
2012-11-13 12:26 | dwuelfrath | Status | new => closed | ||||||||||||
2012-11-13 12:26 | dwuelfrath | Resolution | open => duplicate | ||||||||||||
2012-11-13 12:26 | dwuelfrath | Fixed in Version | => 3.6.1 | ||||||||||||
2012-11-13 12:26 | dwuelfrath | Relationship added | duplicate of 0001602 | ||||||||||||
2012-12-28 16:29 | lmunro | Relationship added | related to 0001619 |
There are no notes attached to this issue. |