Server move problems - error with viewer library

4 posts by 2 authors in: Forums > CMS Builder
Last Post: July 21, 2011   (RSS)

By cornishweb - July 19, 2011 - edited: July 19, 2011

Hello.

I have searched through the forums but can't quite find any other issues that are the same that I am facing.

I have developed a CMSBuilder site on my own cpanel linux server. Everything works great.

The client then moved this to their internal server, so some of the file paths are going to change from public_html stuff to var/html etc.

The site works great on their internal server.

However, if I add a new section editor to the site on their internal server and copy and paste the code generator stuff, the page does not display, but simply loads the following error:

"Couldn't load viewer library, check filepath in sourcecode."

The paths to the files all look correct and the old pages created on my server work and function correctly on the new one. It's only new ones created on their server that are causing issues.

At this moment I don't have access to their server, so cannot copy and paste full source code, but I have checked that it is identical format to the other pages and it is.

Very puzzled.

Thanks for any help!

Re: [cornishweb] Server move problems - error with viewer library

By Jason - July 20, 2011

Hi,

Just to make sure I understand, pages that were created before the site was moved to their internal server work, where as pages created after that point can't load the viewer library. Is that right?

Would you be able to send in a copy of the code generator code that isn't working? If you don't want to post this to the forum, you can send it to support@interactivetools.com

Hope this helps
---------------------------------------------------
Jason Sauchuk - Project Manager
interactivetools.com

Hire me! Save time by getting our experts to help with your project.
http://www.interactivetools.com/consulting/

Re: [Jason] Server move problems - error with viewer library

By cornishweb - July 20, 2011

Hi Jason,

Yes that is correct. They have emailed me today to say that the problem is now solved and that it was related to an FTP password issue.

Will drop you an email if it crops up again.

Thanks for the reply though.

Thomas