honza.skypala

<p>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.</p>
<p>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.</p>
<p>Single posts are untouched, they still show full galleries, at least for now.</p>
<p>You can reach similar functionality just by creating two galleries and putting the <!–more–> 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).</p>
<p>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.</p>
<p>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.</p>
<p>Plugin supports several lightbox implementations.</p>
<h3>License</h3>
<p>WTFPL License 2.0 applies</p>
<pre><code>           DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
                   Version 2, December 2004

Copyright (C) 2004 Sam Hocevar <sam@hocevar.net>

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.<h3>ToDo's</h3>* enable plugin to work in opposite manner - do not automatically slice down galleries, but only on posts / tags where the downto attr is set
</code></pre>
<p>* re-check WP-Minify on possibility to use the compiled JS files (internal)<br />
* enable slicing w/ Ajax loading on single posts</p>


Gallery Slice

Slice down galleries on archive pages to preview-only, with link to load full gallery via Ajax

Dev Kabir

<p>Are you tired of dealing with pesky CORS errors on your website? Do you want to finally be able to access cross-origin resources with ease? Look no further! This plugin is here to solve all of your CORS issues. With just a few simple clicks, you can enable CORS support on your website and say goodbye to frustrating error messages. Plus, This tool is easy to use and compatible with all major browsers. Don’t miss out on this game-changing solution! Try today and revolutionize the way you access cross-origin resources.</p>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/HAcE67gnwT8?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/bFru6VCZ7KA?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/-WGML9mZmPo?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<h3>What is CORS ?</h3>
<p>CORS (Cross-Origin Resource Sharing) is a security feature implemented by web browsers that blocks web pages from making requests to a different domain than the one that served the web page. This is done to prevent malicious websites from making unauthorized requests to other websites on behalf of the user.</p>
<p>However, there may be legitimate reasons for a web page to make requests to a different domain, such as accessing a third-party API or including resources from a CDN. In these cases, the server that the web page is making the request to can include special headers in its responses that tell the browser to allow the web page to access the resources.</p>
<p>If a web page tries to make a request to a different domain and the server doesn’t include the necessary CORS headers, the browser will block the request and the web page will receive a CORS error. This can be frustrating for developers, as it can prevent them from accessing resources they need to build their websites or applications.</p>
<h3>Does the cors error occur on WordPress?</h3>
<p>Yes, CORS errors can occur on WordPress websites. WordPress is a content management system (CMS) that runs on a web server and serves web pages to users through a web browser. As with any other web page, CORS errors can occur when a WordPress website tries to make requests to a different domain and the server doesn’t include the necessary CORS headers in its responses.</p>
<p>There are several reasons why a WordPress website might encounter CORS errors. For example, the website might be using a plugin or theme that makes requests to an external API or includes resources from a different domain. In this case, the server hosting the API or resources would need to include the necessary CORS headers in its responses to allow the WordPress website to access them.</p>
<p>Another possible cause of CORS errors on WordPress websites is if the website is hosted on a server that has CORS headers disabled. In this case, the website would not be able to make requests to any other domains, even if the server hosting those domains includes the necessary CORS headers.</p>
<p>To fix CORS errors on a WordPress website, you will need to either configure the server to include the necessary CORS headers or modify the website to make requests to a different domain that does include the necessary headers. It’s also possible to use a plugin or other tool to enable CORS support on your WordPress website.</p>
<h3>How do I enable cors without a plugin in WordPress?</h3>
<p>There are a few different ways you can enable CORS support on a WordPress website without using a plugin.</p>
<p>Modify the server configuration: If you have access to the server that your WordPress website is hosted on, you can enable CORS by adding the necessary headers to the server’s configuration. The exact steps for doing this will depend on the type of server you are using and how it is configured.</p>
<p>Be aware that modifying the server configuration or adding code to your WordPress website can have unintended consequences, so it’s a good idea to test any changes thoroughly before deploying them to a production environment.</p>
<h3>How does your plugin help with CORS support?</h3>
<p>This plugin adds support for CORS to your WordPress website, allowing you to specify which domains are allowed to access your website’s resources, and which types of requests are allowed. This helps to ensure that your website remains secure while allowing authorized access to resources from other domains.</p>
<p><strong>If your site is serving data to others, then This plugin will work. Otherwise, do not install this plugin, It will be waste of your time only.</strong></p>
<h3>Why Choose ‘Enable CORS’</h3>
<ul>
<li><strong>Save Time</strong>: No more manual configuration of CORS headers. This plugin does it for you.</li>
<li><strong>Improve Security</strong>: Specify which domains are allowed to access your website’s resources.</li>
<li><strong>Ease of Use</strong>: This plugin is easy to use and compatible with all major browsers.</li>
<li><strong>Excellent Support</strong>: I offer top-notch <strong>paid support</strong> to assist you whenever you need help.</li>
</ul>
<p>Try ‘Enable CORS’ today and experience the difference!</p>
<h3>Testing Your Setup</h3>
<ol>
<li>
<p><strong>Source Site</strong>:</p>
<ul>
<li>Install and activate the <strong>Enable CORS</strong> plugin.</li>
<li>Install and activate the <strong>Cors Tester</strong> plugin.</li>
</ul>
</li>
<li>
<p><strong>Target Site</strong>:</p>
<ul>
<li>Install and activate the <strong>CORS Shortcode Plugin</strong>.</li>
<li>It will add a page with a short code <code>[cors_display]</code></li>
<li>Edit and save the page content as follows:<br />
 <code>php<br />
[cors_display base_url="http://source-site.com"]</code></li>
<li>If you don’t provide a <code>base_url</code>, it will default to the target site’s URL. So cors will be failed.</li>
</ul>
</li>
<li>
<p><strong>Testing</strong>:</p>
<ul>
<li>Visit the page where you added the shortcode. If everything is set up correctly, the current time data from the <strong>Source Site</strong> will be displayed.</li>
</ul>
</li>
</ol>
<p>For a detailed walkthrough and additional help on testing your configuration, please refer to the following link: <a href="https://gist.github.com/devkabir/89972aa28d2302cecf13385be1730eda" rel="nofollow ugc">How to Test Your Setup</a></p>
<h3>Note to all users</h3>
<p>I appreciate your understanding that this project is pursued in my spare time, outside of my regular professional commitments. As such, there may be delays in responding to inquiries or implementing updates. I assure you that I am committed to this project, as I personally use this plugin for my own website and for several of my clients. If you are comfortable with this arrangement, I encourage you to install the plugin. However, if immediate support and frequent updates are crucial for you, I kindly suggest exploring other options that may better suit your needs.</p>
<h3>Thank You</h3>
<ul>
<li><a href="https://profiles.wordpress.org/yanabelle/" rel="nofollow ugc">Dakini</a> and <a href="https://profiles.wordpress.org/irinashl/" rel="nofollow ugc">Irina</a> for their contributions to the Russian translation.</li>
</ul>


Enable CORS

Please read the plugin description before installing to ensure compatibility and avoid potential issues. This plugin will be free forever.

Gallery Slice vs Enable CORS