Gallery Slice vs Page Load Ajax

The standard gallery in WordPress has one limitation — it always shows all the pictures in the gallery. I know there are alternative galleries available, which support pagination, but I never thought this is a good approach. The reader never wants to see n-th page of the gallery — if the first page got his attention, then he wants to see all of the rest, not split into pages anymore. At least, this is how I see it. So, if you run a blog, on which you publish huge galleries with many many many pictures, maybe you want to show only preview of the gallery on archive pages (homepage, categories, archives etc.), so the individual posts are not too long. The gallery-preview then contains a link, which loads the rest of the gallery if the reader wishes so, via Ajax. Well, this plugin brings exactly that, all with standard WordPress gallery. Single posts are untouched, they still show full galleries, at least for now. You can reach similar functionality just by creating two galleries and putting the tag in between them — and the archive page shows only the first gallery, while single post shows the whole gallery. But, this plugin has several advantages: it can be set and forget, and then the plugin automatically applies it for every post/gallery published. If the gallery is followed by another text, then this text is still displayed on the archives page. Loading of the rest of gallery is handled by Ajax (with fallback to single-post URL if Ajax fails). In options, you specify two values: first one threshold — amount of images, if the gallery exceeds this many, it is sliced into a preview. This is the second value, how many images should be shown in a preview. This allows to have 2 different values for that, e.g. 9 images for preview, but 12 images for threshold, which makes some flexibility, that if the gallery is 10 images big, then it is not shortening by jsut one image. Anyway, you can also specify the same values, if you wish. These two values are specified on three levels: global (per blog), per post and per gallery tag. You can also specify not to slice a gallery in specific post, resp. not to slice a specific gallery. Plugin supports several lightbox implementations. License WTFPL License 2.0 applies DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE Version 2, December 2004 Copyright (C) 2004 Sam Hocevar Everyone is permitted to copy and distribute verbatim or modified copies of this license document, and changing it is allowed as long as the name is changed. DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. You just DO WHAT THE FUCK YOU WANT TO. ToDo's * enable plugin to work in opposite manner - do not automatically slice down galleries, but only on posts / tags where the downto attr is set * re-check WP-Minify on possibility to use the compiled JS files (internal) * enable slicing w/ Ajax loading on single posts

The purpose of this plugin is to minimize page load time and resource usage by updating the page title and content only rather then reloading the entire webpage. The new contents and titles are fetched by ajax calls. Restriction: As the rest of the page like header including all styles and scripts, footer and sidebars are not affected, you should only use this to switch between pages with the same overall layout and requirements. You can enter shortcodes in the page content that will show up as a button or a text link. When activating the link, the pages title and content will be replaced by the title and content of the specified page. There are four possible independant arguments to the shortcode: – page (required). This can be the page title or the page id. – text (optional). The button text or textlink text. – title-elm (optional). The title element id or class if it is not the default as entered on the settings page. – content-elm (optional). The content element id or class if not default. Examples: [pla page=”Tet page”] [pla page=”5″ text=”Go to the testpage”] [pla page=”My Page” content-elm=”#my-div”]