nnaxitloesungen

<p>nnax ReadMore helps editors keep posts and pages compact while still making additional content available on demand.</p>
<p>Use the shortcode <code>[nnax_readmore]...[/nnax_readmore]</code> to hide longer sections behind a toggle button. Visitors can expand and collapse the content without requiring a bundled frontend framework.</p>
<h4>Main features</h4>
<ul>
<li>Namespaced shortcode <code>[nnax_readmore]</code> for expandable content blocks</li>
<li>Dedicated ReadMore block for Gutenberg and a button above the editor in the Classic Editor</li>
<li>Toggle button text between “Mehr anzeigen” and “Weniger anzeigen”</li>
<li>Configurable button CSS classes in plugin settings</li>
<li>Role-based visibility and editing permissions for the plugin admin area</li>
<li>Toggle behavior works without any bundled frontend library</li>
<li>Clean uninstall behavior for plugin options</li>
</ul>
<h3>Requirements</h3>
<ul>
<li>WordPress 6.0 or higher</li>
<li>PHP 7.4 or higher</li>
</ul>
<h3>Usage</h3>
<p>Use this shortcode in content:</p>
<pre><code>[nnax_readmore]Your hidden content[/nnax_readmore]
</code></pre>
<p>In Gutenberg, a dedicated <code>ReadMore</code> block is available in the block inserter. In the Classic Editor, the button is available above the editor. In both cases, a dialog opens for entering the hidden content.</p>
<h3>Uninstallation</h3>
<p>When the plugin is deleted, <code>uninstall.php</code> removes the options <code>nnaxreadmore_button_classes</code>, <code>nnaxreadmore_general_settings</code>, and <code>nnaxreadmore_role_access</code>.<br />
In multisite, cleanup runs per site and also removes a possible network option.</p>
<h3>Known Limitations</h3>
<ul>
<li>The plugin focuses on the shortcode toggle behavior only.</li>
<li>Runtime compatibility with the minimum supported WordPress version, multisite setups, and broader theme sets must be validated in the target project environment.</li>
</ul>


nnax ReadMore

Hide long content behind a simple Read More button and reveal it on click.

Nick Cousins

<h4>Because “read more” isn’t good enough</h4>
<p>Turn your “More” links into a bespoke call-to-action for each post. Rather than have “Read more” or “[…]” after your excerpt, you could have “See Bob’s garden up close” in a post about a beautiful garden, or “Try our tasty sauce” in a bolognese sauce recipe.</p>


ActionPress

Still works

Replace the [...] more link with custom text for each post, creating a specific call-to-action.

nnax ReadMore vs ActionPress