|
uligrepel Posts: 3
5/8/2017
|
Hi,
long time, no hear... I've recently been working on a long time (i.e. 10 years old) statical web site project again, and I'm having trouble with dynamic menus: 10 years ago they just worked fine, now, probably after conversion to the new dynamic menu technique, they don't. The link is always referring to the page with the filename "default.htm", even though the publication profile (and the rendered page) is using the filename "index.html".
With Chrome, clicking on a menu link gives you the local equivalent of a 404 page, with Edge, you'll get a white page only.
Fixing the link from "default.htm" to "index.html" in the generated JavaScript files (e.g. slm_388.js) helps, however I'd prefer not having to do that manually ;-)
edited by uligrepel on 08.05.2017
|
|
|
0
link
|
|
Jürgen Wolz Posts: 32
5/10/2017
|
Hi,
We tested dynamic menues and were unable to reproduce the behaviour you reported.
On a page that has the problem, please right click the object to which the dynamic menu is attached, select "Dynamic Menu" / "Apply Dynamic Menu". For the menu, that will be displayed as "Applied dynamic menu", choose "Edit Menu".
Please select an affected menu item from the menu structure list and send us a screenshot to the support mail address: Support_D@studioline.net
Please do also check the link type: type "Link to page" will be refreshed to the profiles default document when the active publishing profile was updated, whereas type "Link to URL" is static and won't be updated by the system. Those will need manual updates in the Dynamic menu.
Please make also sure that the page with the incorrect link in the dynamic menu is also newly published.
In case the wrong link will not be corrected after updating the menu and publishing the page, please do send us the URL of the page that has the problem to above support email address, so we would be able to inspect.
Best Regards
H&M System Software GmbH
Jürgen Wolz
|
|
|
0
link
|
|
uligrepel Posts: 3
5/11/2017
|
Hi Jürgen,
the web site I'm working on is, for privacy reasons, actually not going to be published on the internet, it is meant for DVD distribution to about 100 people.
I added a new publishing profile, since I wanted a clean start in the publishing directory which I grabbed from the StudioLine directories to burn on the DVDs. So yes, every page was published. Actually, the pages themselves are just fine, just the generated JavaScript files for the menues were using the wrong default page name (default.htm instead of index.html) - otherwise I'd have had to manually update >300 individual files.
All original publishing profiles were specified as using "index.html" as well. 10 years ago the menus worked just fine as well.
And yes, the menu uses "link to page", not "link to URL".
When adding new entries to the menu I was asked whether I'd want to update the menues to the new technology which was faster. I said "yes". Maybe this caused the problem.
I also have to admit that I was not using the most current version of StudioLine - it was about 1.5 years old already. Didn't want to change a winning team when under time pressure for the DVD production... ;-). However, creating yet another fresh publishing profile and updating the menu and republishing everything didn't switch the generated dynamic menu JavaScript files from using "default.htm" when "index.html" would've been correct.
I'm going to send some screenshots and some files via email.
Greetings
Uli
|
|
|
0
link
|
|
Andy Schmidt Administrator Posts: 114
5/12/2017
|
This issue is specific to publishing the HTML pages to file (DVD) rather than through FTP. In this case, the name for the default document, "default.htm", carried over from the standard publishing profile for this project, instead of from the specific publishing profile.
As a temporary work-around one could temporarily change the setting of the standard publishing profile from "default.htm" to "index.html" prior to publishing the DVD.
Note: The "default document" name in a Publishing Profile is meant to match the setting on the target web server. It would be the job of the web server, to redirect a request for a non-specific HTTP URL (one lacking an explicit document name), to a fully qualified URL (which includes one of the default document names configured for that web site).
As is apparent, the concept of a "default document" doesn't apply with offline viewing, as no web server is involved. In this context, file system requests are always explicitly for a particular file, no matter the name (default.htm, index.html, or any other).
edited by Andy Schmidt on 5/12/2017
edited by Andy Schmidt on 5/12/2017
|
|
|
+1
link
|
|
uligrepel Posts: 3
5/13/2017
|
Hi Andy, hi Jürgen,
thanks for the answers, and thanks for the emailed support as well. I was able to help myself even before entering this forum, since in my case there's just four JavaScript files involved that have to be fixed (four menues, one JavaScript file for each of them). I'd only have to take care that after changing a menu (and republishing it) I'd have to manually change default.htm into index.html again, that's why I said I wouldn't want to have to do that manually...
If you're creating a fix in the next version of StudioLine I'm just fine.
("Publishing to DVD (i.e. file) only" - the menus should work on the locally published preview as well as on a real server, where, as you point out correctly, it's the server's job to actually fix a URL from "www.whatever.com/pagename" first to "www.whatever.com/pagename/" (for "pagename" is a directory and not an existing to-be-delivered file), and then (internally only) fixing it to "www.whatever.com/pagename/default.htm" or whatever is configured to be the server's default filename. And "default.htm" is Microsoft's IS preferred name, while "index.html" is Apache's preferred name...)
|
|
|
0
link
|