KB:Troubleshooting
From PageLime Documentation
General
I have a script or bit of code that seems to conflict with the Pagelime Site Editor
- You might be experiencing a situation where you have some code on your site that works totally fine on the public side of your site in a browser but gets a bit wonky or breaks entirely when you load your page through the Pagelime Site Editor. Sometimes certain scripts or code don't get along with Pagelime. But this is OK, below are two fairly simple methods to work around these conflicts
Conditional Commenting
- Simply wrap whatever code you have in question with
<!-- CMS:REMOVE --> <script>script here</script><!-- CMS:END-REMOVE -->
- This toggles your script as invisible within Pagelime and actually removes it from the page when you are in the Pagelime Site Editor
Javascript Method
- Use a JS check such as
if (!window.isCmsPageEditorPreview) {
// put your scripts here
}
- This function checks to see if you are viewing the page withing Pagelime Site Editor, if so, it does nothing and the scripts inside the if statement are not executed. However, if someone is NOT viewing the site through Pagelime, the script WILL be executed.
The Pagelime WYSIWYG editor is being funky and/or doesn't show my content!
- There are several possible issues that could be causing abnormal WYSIWYG editor behavior, below we've listed a few of the most common ones.
XHTML Validation Error
- This error is typically caused by the misrendering of tags and validation rules. Although Pagelime is usually super tolerant of these type of errors, they can happen.
- To resolve, we recommend running your page through a validation tool, such as WC3 Validation Tool and then tracing any errors to tags. If everything looks ok, try changing the taq in question to a "div" if it is not already. DIV tags can be a bit more forgiving and versatile.
Pasting from Microsoft Word or "Phantom Formatting"
- Microsoft Word is notorious for copying text with lots of hidden formatting that can cause a mess in most WYSIWYG editors. Luckily, Pagelime has a special button for importing content from word into the editor.
- Simply
- Go to "site settings"
- Then click the WYSIWYG tab
- You'll see that you can configure which tools are available to your clients. One of the tools is a paste icon with an MS word sub-icon. It should be on by default, but if you use that "paste button" it will automatically clean up all the bad MS Word code.
WYSIWYG Issue #3
My webhosting has an FTP lock. Do you have a static IP?
- We sure do, if you would like it, just Contact Us and we can send the IP address to you.
I keep deleting pages from my sitemap in Pagelime, but I'm still seeing them on my server and FTP, what gives?
- Since we designed Pagelime with the client in mind and in you, the designer's, best interest, we don't delete pages on your server, we only delete them from the sitemap. That way if your clients make a mistake in deleting a page, you don't lose everything. The page is still recoverable. In order to delete the actual file, you have to manually delete items from the server.
- Our theory is that if you strictly think about it, a page doesn't exist if nothing links to it. We don't allow deletion because most clients will delete, but forget to remove links, then you get nasty 404's. We like to think the other way around: remove the links, but don't delete the page unless absolutely necessary = happy websites, better content management/backup.
- You may also note, that we apply this same methodology to images and other assets. We do not "hard delete" uploaded items off the server, they will be removed from the Pagelime interface but still present on the server. If you are using a web app or script that pulls it's index based on the contents of a folder or presence of files, a common workaround is to instead reference the Pagelime XML files which is updated everytime a page or asset is moved, changed or deleted.
- That said, we may build a "true page deletion feature" and add that in the future, but it's a rare request. If you would like to request it, submit it on our User-voice (the feedback tab to the left).
Pagelime is running slow in IE.
- Due to the way IE handles certain Web 2.0 technologies, and certain IE specific workarounds we have implemented, it can cause Pagelime to run a bit slow. We highly recommend using either Chrome or Safari for the fastest performance. Firefox is a close second for speed and is recommended for development and troubleshooting code when paired with Firebug.
I'm using Active FTP and Pagelime is not working.
- We currently do not support explicit Active FTP. We suggest any client that needs Active FTP talks to their host and asks them them enable Passive FTP. It is our experience that hosts have no problem with complying. We steer clear of Active FTP for a variety of reasons we will share with you: its less secure, can cause system instability because it only allows for 1 active connection at a time locking on to the port, additionally, this slows down the system and can cause a further issues.
Do you support FTPES?
- We currently do not support FTPES as it is an extremely new and rare transfer protocol which forces SLL/TLS connections. If you have further questions about this, or any other support/features, please Contact Us.
Adobe Flash Related
I have a Flash piece that pulls in a config file. It doesn't seem to work in Pagelime.
- If a Flash element is pulling dynamic content from your site, you have to add a cross-domain policy file permitting Pagelime to access your site, it's pretty simple, check out Adobe's Cross Domain Policy Article for more details.
My Flash piece is showing up over everything else and it makes it hard/impossible to edit my page!
- This is fairly common flash issue and can usually be resolved by adding the parameter
wmode=opaqueto your Flash embed code. To learn more about the issue, you can reference this thread on Stack Overflow
- This is fairly common flash issue and can usually be resolved by adding the parameter