Hash URL won't trigger modal

[Rule72]

Hiya!

I have a series of URLs on page A, that is supposed to navigate to page B and trigger a modal hash. Loopers on page A are generating the URL like so: …url/#{id} , and page B is also filling in the hash with the ID.

Here’s the start point (page A)

And the end point (page B) should be bringing up the modal, but neighhhh

It WAS working for most of the development. A peculiarity I’d noticed is when hovering over the modal toggle on page B that, for a time, it would show the URL preview in the browser (bottom left), however that is no longer the case. Now, page A’s URL simply navigates to page B and that’s that, rather than triggering it’s partnered modal window.

Help?

[friech]

Hi Jake,

Thank you for writing in, how did you configure the modal’s Toggle Hash? It looks like the ID (#602) you put on the button on Page A, did not match the modal’s Toggle Hash (1460) on the Page B. That needs to match.

If the issue persists, please provide us login credentials in a secure note so we can take a closer look.

Cheers!

[Rule72]

The Page A and Page B configuration are both using the same looper query and dynamic variable:

On Page A, it’s built in the actual page. On Page B, however, it’s input into the “tabs” module via a Global Block shortcode:

---

Regarding the hash mismatch, how are you getting the Page B number in the first place? When I pop into the inspector, I can’t find the toggle ID at all.

[ruenel]

Hello @Rule72,

It took us some time to figure out the cause of your issue. After further investigation, we have found out that you have inserted this [display-posts id="{{dc:post:id}}" include_content="true" include_title="false"] shortcode in your modal content element that breaks the looper which is why the looper no longer outputs the correct post ID. You need to remove this shortcode. Replace it with dynamic content if you are going to display the post details like the excerpt and other details.

Kindly let us know how it goes.

[Rule72]

Ooh, nice catch on that one! Sure enough, swapping out the post content plugin with an actual function registration fixed the issue.

[marc_a]

Hi @Rule72,

We’re glad that my colleague was able to help you with your issue! If you have any other concerns or clarifications regarding our theme features, feel free to open up a new thread.

Thank you.