I'm trying to navigate using the visual composer to authenticated pages, but whenever I try to login in via the browse functionality, it fails and loops back to the login screen (I know this works fine in production).
Is this an issue with Adobe or is there another workaround.
One option I was considering was saving a local version of the page and making the changes on that then applying it to the correct URL - but it doesn't look like you can edit local versions of the pages in Visual Composer - any other ideas?
Thank you for your note.
Select the “Configure” icon on the top of the Target interface and select “URL”
Then in the advanced options select the ‘URL contains xyz” condition (as shown below). So now the test would run on all the pages that match the URL condition specified irrespective of the key-value parameters that could be appended to the URL.
This is actually called Template testing and the relevant help link is here:
Hope this helps!
Thanks Shekhar. This helps.
We could get around to the 2nd page by passing few URL parameters unfortunately not for 3rd or 4th page in the journey.
I have few more follow-up questions. hope you will be able to help.
1) Is there any other mechanism/work around to target content of those pages which falls under this known limitation ?
2) Does the visual composer page configuration includes the URL parameters while registering a page ? Basically, wondering whether user has to configure for every combination of the url parameters & its values?
I believe I'm having the same issue, I'm trying to use the visual experience composer on a staging page to set up a campaign before content is live and when I type in the staging URL I'm prompted to input my login credentials. Once I do so I see a blank screen and the visual experience composer can't render the staging page. Can you share the details of the workaround you used to resolve your issue?
Here is the update on the above ask.
If you have a URL that can directly load on a browser properly then the known issue is not applicable here.
The issue is only applicable where on load of the URL you get a page load error because of some validation rules. You can check this by copying the 2nd page of loan application and load it in a different browser and see if the page is loading properly or throwing any error.
In short, in case you have setup validation rules to access the 2nd page then the known issue is applicable here. But if the 2nd page is only has navigation limitation of not showing up before the 1st page then the known issue doesn't apply.
Hope this helps!
Is this known issue limited to the authenticated page flow only or applicable to any page which could be accessed only after filling some prerequisite information?
Say, I want to configure campaign for the 2nd page of the loan application journey where users can access anonymous access to all pages but can navigate to subsequent pages after completing 1st page.
Could you please let us know whether this issue was resolved or not?
It seems this has something to do with the below known issue:
This occurs when the URL of the saved activity cannot be opened directly but can only be opened after logging in and reaching that page or after filling some prerequisite information. Target does not save the navigations a user makes inside the Visual Experience Composer, except for the final page on which changes are done all other navigation are not saved.