Auto Pagination Being Triggered By Post Images Encoded In Base64 - Redux

The problem of auto pagination, triggering display page segmentation, has been with us since early 2010. Even in the beginning, auto pagination was not 100% popular with blog owners. As more blog owners got used to the inevitability of auto pagination, more scenarios were discovered, where it critically affected blogs. The most recently identified scenario, where auto pagination was involved, was with images hosted as Base64 content - first discovered a year after the initial opposition started.

Having examined enough cases of Base64 hosted photos during the past year, we now see that the problem appears to be caused by use of the drag and drop technique, or the "From the web" option in the "Insert image" wizard in post editor, when adding photos to blog posts. Both drag and drop, and "From the web", appear to consistently add images hosted as Base64 content, into blog posts.

With the causative scenario identified, we can now recommend a technique for resolution. Hoping that any blog showing the problem of critical display page segmentation does not have an unacceptably large number of images / photos hosted as Base64 content, each image or photo has to be identified and removed, and a properly installed image / photo replacing it.

1. Find the original of each photo installed, using drag and drop or "From the web".
2. Copy each photo to your computer.
3. Edit each post containing each photo. Remove each photo, as previously added.
4. Add each photo again, using "Insert image", and selecting the copy on your computer.
5. Re publish each post, so edited.

If the blog in question contains too many images or photos hosted as Base64 content, a possible alternative might be to change the blog to display using a dynamic template. This may provide a solution because dynamic templates, with the content rendered on the client computers, do not appear to be susceptible to display page segmentation.

>> Top