Forum Replies Created

Viewing 15 replies - 61 through 75 (of 372 total)
  • Plugin Author caterhamcomputing

    (@caterhamcomputing)

    Your code:

    [child_pages id=”33714″ thumbs=”true” link_thumbs=”true” link_titles=”true” post_status=”publish” hide_excerpt=”true” hide_more=”true” depth=”2″ skin=”blue”]

    My code:

    [child_pages id="33714" thumbs="true" link_thumbs="true" link_titles="true" post_status="publish" hide_excerpt="true" hide_more="true" depth="2" skin="blue"]

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    Hi … I believe that I may have misunderstood the problem.

    As promised, I have been testing the plugin to try and reproduce the error – but was failing to do so.

    However, when I copied your example from your earlier post … it failed.

    I think the problem may be that not all of the quotes in your example are standard double quotes … so the passing of parameters is not working as expected.

    I manually replaced the double quotes, and everything worked as expected.

    If I am getting this wrong and the quotes thing is just a display thing on this forum, please let me know …

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    Hi.

    Sorry to have taken a while to get back to you on this.

    I have used jQuery in the past to change the height of each box when the page is first displayed or the browser is resized.

    I am looking at introducing new CSS when the plugin moves to version 2.0 later in the year, and will probably use CSS Grid or Flexbox for the layout which will make this a bit easier to achieve.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    Sorry to have taken so long to reply … The plugin has always been compatible with the latest version of WordPress, but I have now tested up to 5.4.2 and updated the details accordingly.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    No problem, I am glad that it is working for you.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    Hi @adventureridingnz

    The depth parameter actually adds the sub-pages as a list, rather than a fully formatted child-page with images, etc.. The reason for this is that it would be very difficult to accommodate lots of sub-pages (and their own sub-pages) while still showing the hierarchy of the pages.

    Imagine the following scenario:

    • The cols parameter is set to 3
    • The depth parameter is also set to 3
    • Each page or child page to be displayed has at least 3 child pages

    The first set of pages would be displayed in 3 columns, but adding the next set of child pages to each box effectively produces 9 columns of sub-pages … going down another level gives 27 columns, and so on.

    This can get pretty unwieldy, and so the compromise was to show the sub-pages of the child-pages as a list.

    This was not a feature that I actually wanted to add, but it was requested by someone as a particular requirement … if I get time i the future, I will look at a better way to do this.

    However, I am a bit surprised by your last reply and will test this out for myself.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    That is absolutely correct … the only thing I will add is that you shouldn’t need to turn the skins off as long as you specify the class and not the skin parameter (although if you don’t use the skins anywhere else on the site, it would be a performance boost to not load the unnecessary CSS file).

    Thanks @adventureridingnz for answering questions while I’ve been unavailable 🙂 … it’s much appreciated.

    Forum: Plugins
    In reply to: [CC Child Pages] New Tab
    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    Thanks @adventureridingnz … I haven’t been around for a while to be able to answer this. You nailed it 🙂

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    There is not an obvious way to do this currently. I may consider doing something with this in the future … in the meantime, there are lots of filters throughout the code that may help you to do this at the moment.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    Sounds like you need to use the exclude parameter … the following is taken from the documentation:

    To exclude pages, use the exclude parameter. This allows you to specify a comma separated list of Page IDs to be excluded from the output of the shortcode.

    [child_pages exclude="5,33,45"]

    There is also an exclude box for the widget.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    Hi.

    I Have just created a similar environment … and on my system I can not access any of the readme.txt files for plugins. As a default setting, this makes sense to not allow direct access to these files for security reasons.

    The fact that you can actually access the Classic Editor readme.txt directly seems strange to me, as I thought that these files were protected from direct access by default.

    I have many site running using this plugin, and have experienced no problems such as this before. I will keep looking into it … but very difficult to pin down at the moment.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    Thanks werdpres … I am wondering if it might be some kind of conflict with TinyMCE Advanced, as it is also adding buttons to the TinyMCE editor.

    I have never come across problems with using the classic editor plugin, but can’t rule it out until I have tested thoroughly.

    Did turning off the “Add button to visual editor” option make any difference? If you do this the javascript file should no longer be loaded.

    You are quite right that I will eventually be adding a block for the Gutenberg editor … so the shortcode will eventually become secondary, although I suspect that shortcodes will be around behind the scenes for quite some time yet.

    I am currently working on the new version of the plugin, so hopefully I can iron out this problem if it is my code that is causing it.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    Hi. Thanks for letting me know about this …

    I have never come across this before, so will try and test out as many scenarios as I can.

    The file that it is trying to load adds the CC Child Pages button to the visual editor, so a workaround may be to go to Settings->CC Child Pages and turn off the “Add button to the visual editor” if you are not using the button.

    @emielb – I think that WordFence may be blocking access to the file in your case as you can set it to deny access to files in various directories. Again, if you don’t use the button turning it off might be the best option (to keep the extra security that WordFence gives you).

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    OK, I have a working fix for this which places uses the image’s alt property for the image and it’s title property for the title attribute of the link.

    Thinking about this a little further, I am going to make this something that you have to turn on with a shortcode parameter for 2 reasons:

    1. Backwards compatibility: I don’t want to change the behaviour of any existing sites unless it is unavoidable.
    2. Semantics: the title attribute in the link should actually reflect the page that it is linking to (I understand that you have made this the case with your images, but in theory the image titles should reflect the image).

    I am going to make these changes, and then once I have completed and tested all the other changes I will release the new version.

    Plugin Author caterhamcomputing

    (@caterhamcomputing)

    You are right to point this out … because the shortcode can pick up images from various places and plugins (as well as the standard featured image), this was originally coded to default to using the title of the post for both the alt and title values.

    I am working on the next release of the plugin, and am looking at re-working this part of the code. There will still be times when using the post title is the only option, but for most images it should output the alt and title values stored for them.

    I may also look at adding some additional parameters (perhaps hide_alt and hide_img_title or similar) to allow suppressing the attributes altogether, although I will assess whether this is likely to be desirable when I code and test the changes mentioned above.

Viewing 15 replies - 61 through 75 (of 372 total)