Forum Replies Created

Viewing 15 replies - 166 through 180 (of 372 total)
  • Plugin Author caterhamcomputing

    (@caterhamcomputing)

    This is certainly a good idea!
    My thoughts are to add a parameter called link_target which would accept all of the values that you could use in the <a> tag.
    I will also add a new use_custom_link_target parameter to allow the value for the HTML target attribute to be set per page/post using a custom field (that way you could set some links to open in a new window, and others to open in the existing one).
    I was hoping to have the new version available about a month ago, but have not been able to work on the project recently due to unexpected work and private commitments. Hopefully I can add this to the version I have ready for testing and get it rolled out shortly.
    Watch this space ….

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    I am marking this issue as resolved, as I have not heard back from you.
    The plugin has been successfully tested on numerous sites built with Divi, so without any further detail it is impossible to comment further.
    If you are still having problems, please let me know what the problem is and I will see what I can do to resolve the issues.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    There are a set of parameters for doing this … see the “Custom Fields” section in the description (at the bottom just before the “Pagination” section).

    The parameters are: use_custom_excerpt, use_custom_title, use_custom_more and use_custom_link

    (These have no effect if list="true")

    Just pass the custom field name as the value of the appropriate parameter (e.g. use_custom_title="my_custom_field") and the plugin will use the custom field instead (if the custom field is not set, the default value will be used … in the case of the example given, the title of the page/post).

    I hope this helps.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    Hi. Sorry not to have been around to reply sooner.

    If you want to not use the skins provided, use the class parameter instead.

    If you set class="myclass" all the CSS that handles the layout will still be applied, but instead of adding one of the skins you will be able to define your own CSS to handle the layout. (See the example at http://ccchildpages.ccplugins.co.uk/)

    The plugin does not resize images … you can choose from the the pre-defined image sizes using the thumbs parameter. Setting the thumbs parameter to the named size will cause the images to be shown at that size (WordPress itself creates separate resized versions of the images.)

    From the WordPress codex:

    The default image sizes of WordPress are “thumbnail” (and its “thumb” alias), “medium”, “large” and “full” (the image you uploaded).

    See https://codex.ww.wp.xz.cn/Post_Thumbnails#Thumbnail_Sizes

    You can create your own thumbnail sizes with a couple of lines of code added to the functions.php of your theme (see https://codex.ww.wp.xz.cn/Function_Reference/set_post_thumbnail_size#Default_Usage) … or there will probably plugins available to allow you to create custom thumbnail sizes that you could then use.

    I hope that this helps.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    Can you give me a little more information about how it is not working? Is it the shortcode or the widget that you are having problems with, and how does the problem show up?

    I have used the plugin on several sites built with the Divi theme without any problems.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    Hi … I’ve been looking a lot into nested child pages, and the problem arises that one of the nested pages may be the page currently displayed – which can cause an infinite loop.

    I am adding a feature to the next release to extend the use of the existing depth so that it will not only apply when using list mode. The top level child pages will then show up as usual, but if the depth parameter is set (to -1 (any depth), 0 (all pages), or any value greater than 1) a list of the child pages will be displayed within the box. This uses wp_list_pages to display the list of child pages, and since the page content is not shown there is no problem with recursion and looping …. this also gets around potential display issues where the child pages are displayed in columns (e.g. trying to show 3 columns in a box that is already only a third of the page width).

    I will be finalising the next release soon, so hopefully this will go some way to achieving what you want to do …

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    The next release of the shortcode will introduce the show_page_content parameter. If set to "true", the entire contents of the page (or as far as the “read more” link, if one is set) will be shown for each page – complete with all HTML formatting.

    I am doing some final testing, and should be releasing this shortly …

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    The shortcode gets the excerpt (whether it is a custom excerpt or generated from the actual page content) in real time … it does not store the excerpt away anywhere for future use, so the page must be cached somewhere.

    Did you try refreshing/reloading the page in the browser after clearing the cache?

    Are you using anything such as Cloudflare or a similar service?

    … another thought: make sure that the use_custom_excerpt has not been set, as this will pick up the excerpt from a custom field (if it is filled in). If this is used, you will need to update the custom field contents.

    Can you post the complete shortcode that you are using.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    Sorting by menu_order will list the pages in the order that they show up when you view your pages in the WordPress dashboard.

    I am assuming that your sidebar menu is a WordPress Custom Menu … if you wanted the pages to show in the same order as this, you’d need to organise the pages into the same order.

    I personally find that the Simple Page Ordering plugin is helpful for this, although there are other plugins available for rearranging pages quickly.

    Please let me know whether I have understood the problem correctly … if not, please provide further information – and, if possible, a link to your page.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    bgeggen … can you provide some detail for the problem you were having, as you deactivated the shortcode before I had a chance to look at it.

    Can you post the shortcode with all the parameters that you were using.

    You mention setting post_per_page in your initial post … is it possible that you mis-typed this when you set up the shortcode, as the parameter is actually posts_per_page.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    As I haven’t heard back, I am assuming that this issue is now resolved. Please let me know if you are still having problems.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    As I have not heard back, I am assuming that this problem is now resolved … please let me know if you are still having difficulties.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    I am hoping that the pagination options added in the latest release will help you to manage large numbers of child pages … simply specify the posts_per_page, and the results will be paginated with next, previous and page number links.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    I am assuming that this issue is now resolved. Please let me know if you still feel that this is a problem with the plugin.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    You can now set the posts_per_page parameter to display paginated output, for example:

    [child_pages posts_per_page="6"]

    … note that this is not an AJAX request.

Viewing 15 replies - 166 through 180 (of 372 total)