Bas T

Ik ook!

Thanks a lot for your fast answer!

1. I’m going to try out the code in the posts you mentioned, especially the first one of the ‘inline trigger with block target’. Thanks, that seems to solve number one!

2. As I understand the Collapse-Commander helps with a WYSIWYG editor, so you don’t have to learn the shortcodes. I have no problem with shortcodes, except that there doens’t seem to be one for the ‘inline trigger’ or the ‘roll your own method’. Could it be possible to add a shortcode in a next version of Collapse-o-matic so we can use it in the same way as [expand title=’…’], so we can see where it’s placed in the visual editor of TinyMCE, and we don’t need to add span classes anymore?

3. I already have ‘filter content’ unchecked, however, if I use the normal [expand title=…’] shortcode an extra <p> appears at the frontend.

Thank you very much again for your work and answers!

I would like to know how that’s done. Would you care to explain, @mangematin, or do you know how to, @twinpictures?
Thanks for your answer!

Thank you, @mbrsolution!

Thanks!

Great!
One question left: Most webhosts use Patchman. Mine too. Patchman already forced an autmatic update upon every customer to mend the phpmailer vulnarability. Does your update work well with that one?

It took me a while to find out where to set these options, but I see the standard setting is no php.
Thanks!

Thanks a lot! Dat was hem!

Hi Keesie, and thanks for your answer!
I did use your method, and adding 999 to it does move the shortcode for related posts after my socialmedia sharing icons. However, it breakes your code, so all I get on my site on the frontend now is “[related_posts_by_tax posts_per_page=”4″ title=”Verder lezen?” taxonomies=”post_tag”] ”
If I delete , 999 the code works again, but of course it’s back to its original position then.
Any ideas?

In functions.php (child theme) I have this now:

// related posts by taxonomy onder bericht
add_filter( 'the_content', 'add_related_posts_after_post_content', 999 );
function add_related_posts_after_post_content( $content ) {
 
    //check if it's a single post page.
    if ( is_single() ) {
 
        // check if we're inside the main loop
        if ( in_the_loop() && is_main_query() ) {
 
            // add your own attributes here (between the brackets [ ... ])
            $shortcode = '[related_posts_by_tax posts_per_page="4" title="Verder lezen?" taxonomies="post_tag"]';
 
            // add the shortcode after the content
            $content = $content . $shortcode;
        }
    }
 
    return $content;
}

• This reply was modified 8 years, 2 months ago by Bas T.
• This reply was modified 8 years, 2 months ago by keesiemeijer. Reason: Fix code block

Kreg fixed this for me wonderfully. I’m not sure if anyone will ever have the same problem, but if you do this is what fixed it: (I hope Kreg doesn’t mind I repost his mail here, but as it will lessen his workload maybe a bit I guess not)

Hi Bas,

This problem is caused by a security check in your browser that blocks cross-site scripting. Basically, you have your website set up to display pages at:

https://www.darelings.nl

and your WordPress admin is at

https://darelings.nl

The browser thinks these are different domains because of the www. difference, so it blocks processing. Notice that if you view your site at:

https://darelings.nl/2012/03/menzis-voor-ieder-menz/

The plugin works fine

You need to make the way your domain displays consistent. Look at your setting in the WordPress admin under General > WordPress Address (URL) and General > Site Address (URL). Try making these both use www.

Good luck,
Kreg

PS: Sorry Kreg, that I mailed this problem through your contact page before I discovered this support page. I didn’t want to hassle you. (although I’m in a bit of a hurry as I need to launch my minicampaign today.)