TOPIC:

There is a fix on the community website (you only need to unzip the 3.4 update package over your current install.

As a test: see tor.nl/~tom/bootstrap

Thanks Tom, very whorthy work you are doing.
Follow your instructions, I installed the patch and exported as 2. Archive export. Complete backup including offline editing and round-tripping back to toolkits or sharing with other Xerte users. I uploaded into my hosting server.

Now I can see on mobiles and pc but on mobile does not launch pictures. I found it is taking the pictures from localhost, I uploaded all pictures in a folder call media but it did not work because the src points to localhost.
Check on www.gogic.co/cvy/strap

How can I change the src to my own http?

Regards

I am still working on it. Not sure yet whther I can or cannot reproduce.

This part of the code is a bit tricky, as it changes the src url used in the editor environment in a relative url for export.

In the meantime, you should be able to open the template.xml and search for all the img tags and fix them

Obviously, that's not a solution, but it might help you gettings things up and running quickly.

OK, as you mentioned I fixed it in the template.xml changing there the sources.
Thanks for your help.

Ok. Good. Gives me a bit more time.

Just checking some points:

- You authored the LearningObject on a local install? In XAMPP?
- Then exported to a publicly reachable server
- Images still refer to localhost

Thank you for answering these questions, because so far I haven't been able to reproduce (but I don't use XAMPP, and I wanted to know whther sequance above is correct, before installing XAMPP).

Yes,
I used XAMPP and worked on local, created a bootstrap object and exported as Archive export. Complete backup including offline editing and round-tripping back to toolkits or sharing with other Xerte users.

The point is when I uploaded into my site server the <img src> points to localhost instead of the media folder in my server.
So I checked all images were in the media folder and type the appropriate route in the template.xml file.

Let me know if you find a patch for this.

Thanks!