Hi, I just purchased Scroller and have figured out how to make my project. But when I try to Publish, it gives me the wrong paths, so I have to manually fix things in Dreamweaver. I'm sure I'm doing something wrong, but can't figure out what. The attached screenshots should illustrate my problem. I made a folder called "scroller" into which everything associated with the project goes, but the source for the javascript file doesn't reflect that. And I've specified the correct path in the Project Properties. Also, where should I go for the likno_scroller_project_content? The program supplies the sample page content paths, but not the actual content paths. I've noticed a few bugs, as well. The help file mentions clicking on the "Compile" button, which doesn't exist. I assume it should read "Publish". When I click "Import Images" to add more photos to my project, all of the links (URLs) I've set up for the existing photos are deleted. Very frustrating. I found a typo on the "Sample Code" tab: It's at the bottom of the page--the tick box "sroller separators". Thanks for your help.

Joe

Reply From: Likno Customer Support

Hello Joe,

First, thank you for your purchase and your feedback.

When you publish your Image based Scroller a folder "lwsc_sample_images" will be created in the Publish folder you have specified and it contains the images for your scroller items.

So, uploading the compiled files to your server should work as expected.

For example you have the www.yourdomain.com, in order to see the index_lwsc_sample.html you need to upload the index_lwsc_sample, likno-scripts (folder) and lwsc_sample_images (folder) to your root folder so after that, opening the www.yourdomain.com/index_lwsc_sample.html should show the scroller as expected.

As for the links that are removed after your click on "Import images" to add more images, I will forward it to the development team.

Hi -- I was trying to put the code in my page and viewing it locally. I don't want to go live with the scroller until I know it's working--and until the site is done. I have everything in a temporary folder called www.mysite.com/2012 while I design the site. Once I'm ready to go live, it will all be moved to www.mysite.com, which necessitates having relatives links for everything. I've attached the file for you to look at, if you need to. I've also attached the page into which I have inserted the code. I wonder if that is perhaps where I went wrong. Thank you. Joestreaming Logan movie

Reply From: Likno Customer Support

Hello Joe,

With the code you have in the page you sent me when you have the page live, you should have in your public_html folder (root folder on your server) the scroller folder which contains the likno-scripts folder (that contains the JavaScript files needed for your scroller). So, the path would be {root folder}/scroller/likno-scripts

Then, you should have your images in the path {root folder}/scroller/photos/{all your scroller photos here}

Hi guys I would like some issues in allwebmenus optimized. Or appreciate your instructions. Problem is quite long upload time. 1.- I am using two menus on every page. horizontal and vertical. (check kamenaric.si) They are mostly using same gif, and awmlib2.js, but files are saved in different subfolders. (awmdata-x +awmdata-y) That doubles download requests and time. solution needed: How could AWM be configured so, that identical files from different menus will be called from same URL? How could I know, if there are other files identical (I know what buttons I use, but what is with awmlib-s? 2.- Could I create compressed .js in AWM? Or does AWM include this option? 3.- Could I move code to the end of <body> to load at the end of html? 4.- Any other method to improve speed of menu loading? Reducing no. of .js files maybe?

Kind Regards, Tomaz

Reply From: Likno Customer Support

Dear Tomaz,

1) Ideally you should not change the AllWebMenus folder settings. You should only change the compiled menu name (which also automatically changes the image submenu) and leave the folder settings to “default”. This way all the menus will use the same library files and load faster. The “awmlib-x” files are different depending on the viewer browser and only one of them is loaded for each user.

2) I am afraid that this option is not included, but if your browser supports zipped resources then you can do this by manually zipping the compiled files. We do have other users that are doing this successfully, but I am afraid I do not know the details of this implementation.

3) You can do this if you want but you have to make sure that the Linking Code is a direct child of the <body> and not within another page element (e.g. <div>). Alternatively, you can select the following option, which will force the menu to load after the page “onload” event is triggered:

4) The JS files that are loaded are only two, the “menu.js” and the “awmlib-x” that corresponds to the current browser, so this cannot be improved further. One thing that you should also keep in mind is that using heavy images in the menu will slow the loading process. If speed is a crucial factor, it is best to use a text-only theme that uses background colors and borders instead of images.