This morning I experimented with location…top, middle, end. All the same result. I also tried making the named parameter required, instead of option, but no change with that either.
I have also come across the same issue in AC2. The URL is shown with the correct query parameter, but the data is not loaded. If I refresh the page with the URL in place, the data loads correctly.
I have searched in the project files and there is no duplicate meta tag for ac:route on any page. There is also no meta tag entry for ac:base in the project.
@patrick any update here? I’m having to trigger a refresh on each page which is undesirable and there are a number of people experiencing this core issue.
Can you test with the latest versions from yesterday’s release. There were several smaller updates related to routing in it. I’ve not been able to reproduce the problem locally, tell me if the update helps or if there are any changes after the update. The update also includes some extra error logging which was missing for when something goes wrong while updating the route view component.
Yes tested with latest version, the issue still remains. I’m not sure where I would find this extra logging to pass on to you - can you let me know where to look? Nothing in console.
Before AC2 this work and still works perfectly.
What I’m doing is fairly simple;
Using a browser component to redirect the page with internal ticked, there is a UID passed in the url
The UID is then used in the server connect to grab the data which should load on the page
In AC1 this loads as expected in AC2 it returns a null value.
The only way I’ve found to fix this is to add a page flow that runs automatically - this checks if the query.jobuuid exists. If it does, it loads the server connect. If it doesn’t then it refreshes the page, checks if query.jobuuid exists again and then loads the server connect.
This only works on page refresh, when using an internal link it does not seem to pick up the query.jobuuid.
