Warnings when opening Help topics

This forum is for all Flare issues related to the HTML5, WebHelp, WebHelp Plus, and Adobe Air Targets
Post Reply
shriya_297
Propeller Head
Posts: 11
Joined: Sun Jul 28, 2013 9:13 pm

Warnings when opening Help topics

Post by shriya_297 »

I also have another problem, realting to HTML Help files integrated with Netbeans. The topics are created using the HTML5 target from Flare 8.0. When I try to open the output files in the application Help, it does so with a series of warnings (attached). I tried troubleshooting it with Dev and the following conclusions were drawn:
So currently we have a number of issues which we need to solve in madcap (and I can’t figure out how to)….
1. The file pages are currently output like attachment 1, but to work they need to look like attachment 2 without the “../”
2. The reference to “jquery.min.js” and “plugins.min.js” do not work. This is because they have two dots in the name. So the files need to be renamed and the output generated as “jquery_min.js” and “plugins_min.js”
Can you please help me sort this out. Ideally what dev needs is to stop those files being generated and remove all references to them, then that would sort the issue out and be the best solution
You do not have the required permissions to view the files attached to this post.
NorthEast
Master Propellus Maximus
Posts: 6426
Joined: Mon Mar 05, 2007 8:33 am

Re: Warnings when opening Help topics

Post by NorthEast »

All of those files are generated when you build the Flare target, and are used by the output.
The '../' in the paths looks correct to me, as they're relative to the topic in the Content folder; they're pointing to the Flare-generated Skins and Resources folders which are at the same level as the Content folder, not inside the Content folder.

If you remove those css and js file references, then the HTML5 help simply won't work - so why do your developers think they need to be removed?
shriya_297
Propeller Head
Posts: 11
Joined: Sun Jul 28, 2013 9:13 pm

Re: Warnings when opening Help topics

Post by shriya_297 »

The developers feel that this is what is causing the errors to appear when you click on a topic in the Help. This is what they say, "Issues with the madcap script files it is putting in the headers? how we can remove them/change them?" How can i resolve this, so the errors do not appear and i can open the topics without any problems. My help topics are integrated with a Netbeans application. These scripts are only added to the HTML5 target files, not in WebHelp generated from Flare or JavaHelp generated from RoboHelp (the latter two have a completely diff set of problems). See the attachment for how the header appears in different output files.
You do not have the required permissions to view the files attached to this post.
shriya_297
Propeller Head
Posts: 11
Joined: Sun Jul 28, 2013 9:13 pm

Re: Warnings when opening Help topics

Post by shriya_297 »

Any solutions/suggestions please.
RamonS
Senior Propellus Maximus
Posts: 4293
Joined: Thu Feb 02, 2006 9:29 am
Location: The Electric City

Re: Warnings when opening Help topics

Post by RamonS »

I took a look at the warnings that you posted originally. Is there a chance that a folder is missing? The help files use relative links and if the relation from its position within the folder structure changed the relative path sends the browsers down the wrong hatch. I built output for the help sample project and it ended up in this (ugly) spot:
C:\Users\Dave\Documents\FlareV9\Application Help Sample.flprj\Output\Dave\MyHTML5
Everything in the MyHTML5 folder needs to be copied as is to the destination.
I am not that familiar with NetBeans, but is there a chance that it maps folders and the mapping could be wrong? The warnings shown state that the files were not found. That means the JS files were never executed. The setup needs to be fixed so that the relative paths point to the right place and then browsers will be able to find the files. That said, are the JS files in question there? Do a file search in the NetBeans environment for one of the files and compare where the files is located and where the browser thinks it is. I am convinced that they are different.
Post Reply