Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter ZAP

    (@michaelzap)

    Indeed! Setting the position to Advanced makes it appear for each variation. Thanks!

    Thread Starter ZAP

    (@michaelzap)

    Is that just not possible given how Breeze works?

    Thread Starter ZAP

    (@michaelzap)

    Yes. Those are both very helpful options, and I use them. However what I want to do here is to exclude certain parts of a page from caching (but otherwise cache the page).

    For example, I may have a page that is something like this:

    header
    title
    content
    * other content that you may like -> should be random! *
    footer

    So what I’m looking for is a way to exclude that specific block of the page (or multiple such blocks) from being pre-rendered and cached, but I want the rest of the page cached. This is not content loaded in a separate iframe or something like that. It’s on-page content, but I would like to be able to do something like include comments in my template files for the beginning and ending of blocks that shouldn’t be cached or use some other method of setting those apart from the caching system.

    I used to do this in a different CMS that I used back in the day (MODx), so I’m hoping that I can here also.

    The best solution that I’ve found so far is just to set the cache time to something short (like six hours) so that at least this content rotates occasionally, but that’s not a good solution (it just kind of makes the problem less obvious).

    Ideas?

    Thread Starter ZAP

    (@michaelzap)

    Yes – that is correct.

    I would like to be able to cache most of a page but not some elements (depending upon the situation I can imagine many such uses, but the easiest example is a random banner image).

    Previously I used a CMS that had caching that worked like this, and I used it all the time for mixing dynamic and cached content.

    ZAP

    (@michaelzap)

    I also want to do this. Actually, I’d like to modify the menus substantially to be something more like this:
    https://www.cuisine-simler.com/

    I’m having trouble figuring out just where exactly in Neve the standard menus are constructed. Or perhaps there’s a hook that I can use to substitute my own menus? I could just completely change header.php, but there are parts of the existing menus that I might choose to keep so I’d prefer to review that code first (and neve_do_header seems to point to hfg_header_render, which doesn’t seem to exist?).

    If the devs can point us to where to do this custom work, we can give it a shot.

    Thanks!

    ZAP

    (@michaelzap)

    Actually, that doesn’t work. It does output empty meta tags, and Facebook’s debugger throws an error at these empty tags (as well as if you already have these same tags elsewhere, for example from an SEO plugin). I had to just comment these out in fbgraphinfo() in class-frontend.php to fix the errors.

    Thread Starter ZAP

    (@michaelzap)

    OK, I think that I’ve answered my own question by playing around with this a bit. Basically the Publish button will publish the post and change the status to Published, and the Save Draft button above the status drop-down allows you to save as any unpublished status. It’s a little confusing, but I guess that’s the WordPress way and I can work with it.

    If that’s not right, please let me know.

    Thread Starter ZAP

    (@michaelzap)

    I understood that, thanks. I think that I can live with all of these statuses being unpublished. I just used Editorial Metadata checkboxes to flag issues that need review post-publishing, and that also works for our purposes.

    What I’m not clear on is whether I need to create a “custom” Published status. It seems as if one is added to the status drop-down menu if I edit a previously-published post, but for new posts none is available. And assuming I do need to add a Published status, should I name it “Publish” so that the slug is “publish” (which I believe is what WordPress expects for a published post)?

    Thanks for your reply.

    Thread Starter ZAP

    (@michaelzap)

    OK, so then do I need to include a Published status among my custom ones so that posts can be published? Or should it actually be called “Publish” so that the slug becomes “publish”? I’m noticing some weirdness with the statuses of previously-published posts, and I want to be sure that this works as expected.

    @karzin: Thanks for posting how to resolve this!

    @devs: This should be included in updated versions of this plugin.

    Thread Starter ZAP

    (@michaelzap)

    Nope. I just edited the home page template so that it would not be included (I removed the standard header call there). Later it was buggy for me in general (refusing to use the folders of images that I gave it and instead using the default images, etc.), but we ended up not using it for this site so I didn’t spend much energy trying to understand what was going on.

Viewing 11 replies - 1 through 11 (of 11 total)