Then I made a gallery but it doesn't show up in my browser; I get javascript errors related to .js files.

The latest SVPicasa template as such works fine and SV PRO V2.1, using svBuilder_PRO also works fine (although I am not yet sure if all the claimed option will work because I didn't yet test it extensively).

I would appreciate if there will be an extensive instructie "How to work with SV PRO 2.1 and SV Picasa template V2"; as a matter of facts I can't understand it is not yet there!!

Re: Can't make latest SV Picasa template and SV PRO V2.1 work together

The SimpleViewer Picasa template has not yet been updated to use SimpleViewer v2.1.Until the updated template is released, you can convert your v2.0.3 galleries created with Picasa to v2.1 by using svBuilder-Pro and following the instructions here: http://simpleviewer.net/simpleviewer/pr … grade.html

Re: Can't make latest SV Picasa template and SV PRO V2.1 work together

Is anything more required?

Yes, SimpleViewer v2.1 uses a 'svcore' folder with HTML, CSS, JavaScript and SWF files (in order to provide an HTML fallback for mobile devices and browers which no not have Flash Player installed) so it is not just a case of swapping over a SWF file.Also, the embedding code is different. The plugin's code will have to reflect these changes.

When can we expect your upgrade of SV Picasa templste?

Hopefully very soon. I am sorry that I am unable to give you a more precise timescale.

Re: Can't make latest SV Picasa template and SV PRO V2.1 work together

berend wrote:

I'm now building a new header.xml with the configuration I need.

I have build a new header.xml and created a gallery via SV Picasa template. In the gallery folder I have also the .swf , simpleviewer.js and jquery-1.3.2.min.js of svBuilder-Pro (out of the 'svcore' folder).

Re: Can't make latest SV Picasa template and SV PRO V2.1 work together

'imagePath' is a variable used by SimpleViewer v1.9 and it has been left active for backwards compatibility only.If you are using the v2 image tag format (which you are), then the 'imagePath' entry will be ignored and you should set the paths to the images and thumbs via 'imageURL' and 'thumbURL' respectively.

In v1.9, the image and thumbnail had to have the same name and all images and thumbs had to be in the same directories.In v2.0, each image and thumbnail URL can be specified separately (via relative or absolute paths) using imageURL and thumbURL attributes in each <image> tag.

Re: Can't make latest SV Picasa template and SV PRO V2.1 work together

Steven Speirs wrote:

In v2.0, each image and thumbnail URL can be specified separately (via relative or absolute paths) using imageURL and thumbURL attributes in each <image> tag.

Steven,

I got the point! It makes it more complicated to generate the right .xml file via SV Picasa template. I wil work on it later today and report progress here.It's now dinner time here in the Netherlands and I'm hungry.

Re: Can't make latest SV Picasa template and SV PRO V2.1 work together

The current Picasa template (although not yet updated to v2.1) generates v2.0 image tag format code (including relative paths for both the thumbs and the main images) to create a self-contained gallery.You can change options in the 'header.xml' file to configure the layout of the gallery but there should be no need to change any paths.

Re: Can't make latest SV Picasa template and SV PRO V2.1 work together

No! That not the issue. I have crossdomain.xml installed in the root and all directory-/ folder-levels down of the "remote server/domain" where the images are stored, already from the beginning. I wonder if I'm hindered in testing the changs I make because of "caching" on my PC, although I added a meta-tag to prevent caching to the index.html file.

Re: Can't make latest SV Picasa template and SV PRO V2.1 work together

Steven Speirs wrote:

You have these characters »»» in the captions and they are causing XML parsing errors.Replace each » with &#0187;

Ok. I see the parsing error and I did the replacement as you suggested. However this doesn't solve anything; after the replacement I still get the parsing error where it's now character 187 in line 41. So I have to count -:)

But I cannot understand that this is te cause of the real issue. I already use this CAPTION for over 4 years in different websites without any problem of parsing errors.

It must be something else that prevents the "remote images" to show up.

Nevertheless ... I will try to find out what's causing the .xml parsing error in XSL format.

UPDATE 1: When I remove the whole CAPTION from the XML file I have NO PARSING ERROR anymore and ...... IT SEEMS TO WORK. Now to find out what causes the parsing problem in the CAPTION.

But I still don't understand why it works perfectly with the 'faulty Caption' with V 1.8 (since april 2006) and V 1.9 (last month) ?????

UPDATE 2: Steven, you were right. The characters »»» caused the problem.

Thanks for your help! I am now back to the functionality I had before with V 1.9, but I have learned much about the possibilities of the V2.1 PRO version in combination with SV Picasa template V 2.0.

Next I need to retrieve the imageIndex with SV Api in order to use browser back-button or javascript history.back() and land on the image I last viewed.