jordannorris

Top man.

Thank you very much for getting back to me so quickly!

Yeah that’s no good as I need a list of filters from front-end checkboxes to check against the $image’s attributes.

Never mind, thanks for your time anyway.

Hi,

I am using the ACF extension. All the images within the gallery have categories assigned to them, I’ve tried sending the list of categories to filter by to the repeater via AJAX and global variables. I figured I could load all images but use a conditional in the repeater to only output html if the current image has the required category. No luck so far though.

Thanks for your reply, any help is greatly appreciated.

@ahctun thanks for your reply, I have included EP_ROOT, and the endpoint is working correctly – the page is displayed using the amp template, so no 404.

I’m not using the loop, so that won’t be it. I should be more specific about the problem.

The header and footer content is loaded using wp_nav_menu(), dynamic_sidebar() etc. – these are working as they should. However, page-specific functions are not pulling content through.

For example, I’m using the ACF repeater field, which checks for content using if ( have_rows('field-name') )

On the front page, this condition is true, and the content is outputted, however when the front page is visited with /amp/ appended to the URL, this conditional is false and the content is not outputted.

** EDIT **
After looking at the Advanced Custom Fields documentation, I realised that specifying the post id in the conditional I mentioned solved the issue.

• This reply was modified 7 years, 6 months ago by jordannorris.
• This reply was modified 7 years, 6 months ago by jordannorris.

Thanks @crishaz for your work!
This works perfectly for me as far as using the correct template is concerned.

However, on my front page, the correct template is displayed, but the front page’s content is not pulled through.

Any thoughts as to why this might be?

Since opening this thread I found that you had solved some IE/Edge problems in 3.1.2 – sorry for the double post.

Now, after updating to 3.1.2, the container type setting seems to be defaulting to use li elements rather than div even though I have selected div in the plugin settings. This is, of course, throwing off my styling. I could fix this by changing the css to work with li elements, however, I would rather not use a list if possible.

–EDIT–
Never mind, I realised that the problem was simply that the repeater template reverted back to the default, rather than pulling through my custom template.

• This reply was modified 7 years, 7 months ago by jordannorris.