HeyBlondie

Thank you again for these suggestions.

I’ll work through them in the coming days and see what I can find.

Hi bcworkz

Thanks for the response.

I must admit that I don’t fully understand these aspects related to rewriting of URLs, but I have found reference previously to the things you mention for how to ‘remove’ the base from a CPT permalinks, but I can find no existence of any such functions in any of the existing files on the site.

(the site uses a custom theme and is based on TwentyThirteen)

I can find no call to add_rewrite_rule() anywhere and no pre_get_posts. That’s why I’m at a bit of a loss as to how the base has been removed in the first place. …and subsequently how to remedy, or reverse, it.

Or maybe there’s something else that I’m really not grasping correctly?

…to add to the OP …

Firstly what I’m wanting to do is to enable the base slug for the MainCPT to see if that solves the pagination issue.

Other than that, if there are suggestions as to why the pagination wouldn’t be working, and how to fix it, that would also be very helpful.

Latest update to v1.0.36 appears to have rectified the problem.

Thank you developers ??

Thank you, but I don’t know what this means? We don’t have “our own facebook app”. We are wanting to display the feed from our FB Page.

Can you clarify what you means please?

Thank you for having addressed this issue so quickly, however it hasn’t made any difference for me either.

I have v1.0.35 and I cannot save changes to the settings. (for reference, I am wanting to adjust the height of the feed).

Thank you!!

The shortcode is in a Text Widget and yes, the ‘code’ tags had been inserted [by WordPress].

Have removed the tags and all functionality is restored (and formatting for that matter).

Thank you.

I understand what you write and agree of course. I am still puzzled that this would be acceptable formatting from a visual perspective, but so be it. I will need to rectify it myself it seems.

Thank you for the response.

resolved

yes thank you. That kind of thing is not normally an issue with plugins on this type and can be easily remedied. The main issue was not addressed however.

The issue was actually the empty ‘p’ tags appearing throughout the content which, interestingly enough, appears to have been rectified in the latest update of the plugin.

Thank you.

Yes, looking forward over here to this fix also ?? …

Thanks. Have done that.

….I have actually discovered the issue.

I am using a theme called Divi, from Elegant Themes. In the options for this theme, there is option for ‘Enable Divi Gallery’ (which was enabled). I disabled this function and the WCF carousel is now working.

This option didn’t occur to me until now. Thanks for looking into it so quickly.

Hi

The link I provided above *is* the page where the gallery shortcode is used. There are two galleries on that page; the grid of images you see first, is the standard WP gallery and there is a carousel gallery below that (of a different plugin).

The shortcode I am using is:
[wcfgallery ids=”4414,4412,4411,4410,4409,4408,4407,4406,4405,4404,4403,4402,4401″]

Thanks

I am really pleased to say that this has now been fixed (and @bcworkz , I’m pleased to say it did in fact end up being a simple solution ?? )

The solution is on this page:
https://www.ads-software.com/support/topic/url-rewriting-on-custom-post-type/

…and here is the eventual code that was added to the functions.php file (in the child theme):

<?php
function fix_request_redirect( $request ) {
        if ( isset( $request->query_vars['post_type'] )
             && 'custom_type' === $request->query_vars['post_type']
             && true === $request->is_singular
             && - 1 == $request->current_post
             && true === $request->is_paged
        ) {
                add_filter( 'redirect_canonical', '__return_false' );
        }
        return $request;
}
add_action( 'parse_query', 'fix_request_redirect' );

(‘custom_type’ to contain the correct name of the custom post type in use)