[VANITY-28] Vanity urls stopped working after installing 5.5.6 Created: 10/Jan/18  Updated: 28/Mar/18  Resolved: 28/Mar/18

Status: Closed
Project: Vanity URL app
Component/s: None
Affects Version/s: 1.4.2
Fix Version/s: None

Type: Bug Priority: Blocker
Reporter: Michaël van der Mark Assignee: Frank Sommer
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

After I installed 5.5.6 to our prod env we noticed the vanity urls stopped working. The only thing we see in logging is

2018-01-10 13:49:12,101 WARN info.magnolia.rendering.engine.RenderingFilter : Resource not found: [/bestelautoverzekering?null]

We are in need of a workaround or a new version.



 Comments   
Comment by Marvin Kerkhoff [ 11/Jan/18 ]

Please check your virtual uri mapping filter inside the magnolia configuration. 5.5.6 is overiding it with a new class.

Comment by Michaël van der Mark [ 11/Jan/18 ]

Do you have more details on where to look?

In the filter configuration I see in VirtualURI
class info.magnolia.virtualuri.VirtualUriFilter

The following class is used in the configuration of the Vanity urls app: com.aperto.magnolia.vanity.VirtualVanityUriMapping

Comment by Marvin Kerkhoff [ 11/Jan/18 ]

Hi Michael,

you are absolutly right. It's all fine with the classes. I was a bit confused because i had the same problem last year as well and noticed it to Frank. Aperto has then released the 1.4.2 release, which now works with Magnolia 5.5.6. I have it installed on our customer production system. Can you double check that 1.4.2 is installed? Did you changed anything in configs around uri mappings or vanity urls?

Comment by Michaël van der Mark [ 11/Jan/18 ]

Yes Im sure 1.4.2 is installed. I haven't changed anything in the configuration. Do you have an idea of which configuration I can check to solve this issue.

Comment by Frank Sommer [ 12/Jan/18 ]

Hi Michael,
please check the definitions app and log files during startup for problems with the vanity url module. Magnolia changed the virtual uri implementation and with that the VirtualVanityUriMapping has problems with its initialization.

Generated at Mon Feb 12 11:10:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.