When I preview my pages, the breadcrumbs and side menu show up and work fine.
However, when I publish to my webserver, it no longer works. The side menu is empty on the pages, so it gets removed from the DOM right away, and there are no breadcrumb links for navigation. Just a 'You are here:' message. The attached image shows what is going on.
I inherited this MadCap project, as someone else started it and it has other pages on it, I was just adding new things to it. The original pages seem to have the menuProxy and breadCrumbProxy working just fine. It is my new pages that are not working.
Here was my development method (I must be missing something, but cannot figure out what it is, so hopefully someone knows!):
I created new topics in the Content Explorer for my new pages. I then went to the Project Organizer, went into the Master ToC, and set up my page flow for the ToC. There was already a MasterPage with the breadcrumb proxy and menu proxy set as the MasterPage for the project target, so it should just be applied. I Preview, and it is applied already and everything looks good! I publish to my web server... breadcrumbs and menu are now empty and auto removed from the DOM...........
I tried manually setting the MasterPage by going to the File View, highlighting all my new pages, and clicking the little wrench icon and setting the MasterPage (following this guide:
https://help.madcapsoftware.com/flare20 ... Topics.htm). Then published, and that didn't work either.
I just do not know what I am missing to get this menu and breadcrumbs working! Any help would be amazing.
BreadCrumbs and Menu proxies not working when published?
BreadCrumbs and Menu proxies not working when published?
You do not have the required permissions to view the files attached to this post.
Re: BreadCrumbs and Menu proxies not working when published?
Have you tried waiting a while after publishing?
If it's anything like our server, it can sometimes take a while for the full site to be 'visible' by the browser.
On our server, I can see new/updated topic files (*.htm) very quickly, but other file types like *.xml or *.js seem to take longer to be downloaded by the browser.
That means things like changes to menus take longer to update than topic content.
If it's anything like our server, it can sometimes take a while for the full site to be 'visible' by the browser.
On our server, I can see new/updated topic files (*.htm) very quickly, but other file types like *.xml or *.js seem to take longer to be downloaded by the browser.
That means things like changes to menus take longer to update than topic content.
Re: BreadCrumbs and Menu proxies not working when published?
Yeah, I've given it a while. Also, tried this morning to the same results even though things were pushed to the server yesterday.
Re: BreadCrumbs and Menu proxies not working when published?
Hi there!
Have you figured out what was the problem?
I encountered the same problem with menu proxy and minitoc proxy, neither of them works when help files are published to our Nginx production web server.
On my VM, I tried hosting Flare output on IIS and Nginx web servers and proxies work just fine. Looks like it might be a problem with our production web server but I could be missing something. Please let me know if you somehow managed to resolve this issue on Flare's side.
Have you figured out what was the problem?
I encountered the same problem with menu proxy and minitoc proxy, neither of them works when help files are published to our Nginx production web server.
On my VM, I tried hosting Flare output on IIS and Nginx web servers and proxies work just fine. Looks like it might be a problem with our production web server but I could be missing something. Please let me know if you somehow managed to resolve this issue on Flare's side.
Re: BreadCrumbs and Menu proxies not working when published?
I'm going to answer my own question just in case someone is struggling with the same issue.
After a research, I figured out that empty proxies have something to do with settings on the web server (in our case, nginx). When the web server is configured to use URLs ending with .html, everything works perfectly—the proxies are populated with links. When a server uses URLs without .html ending (e.g., https://documentation.com/topic instead of https://documentation.com/topic.html), Flare's script cannot generate links for proxies and they remain blank. Hopefully, the team agreed to update web server settings.
Anyway, I would like Flare to be more flexible and support both cases.
After a research, I figured out that empty proxies have something to do with settings on the web server (in our case, nginx). When the web server is configured to use URLs ending with .html, everything works perfectly—the proxies are populated with links. When a server uses URLs without .html ending (e.g., https://documentation.com/topic instead of https://documentation.com/topic.html), Flare's script cannot generate links for proxies and they remain blank. Hopefully, the team agreed to update web server settings.
Anyway, I would like Flare to be more flexible and support both cases.
-
- Senior Propellus Maximus
- Posts: 2632
- Joined: Wed Apr 14, 2010 8:01 am
- Location: Surrey, UK
Re: BreadCrumbs and Menu proxies not working when published?
Sounds like a great idea for a feature request - click the link in my signature to go to Madcap's feature request form.olly_k wrote:.....Anyway, I would like Flare to be more flexible and support both cases.
Started as a newbie with Flare 6.1, now using Flare 2023.
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx