All add-ons currently require PHP 7.4 or greater.

On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.

Publisher does not support the Fluid field type. Please do not contact asking when support will be available.

If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.

Ticket: Easy linking to existing entries in Wyvern?

Status Resolved
Add-on / Version Client has number
Severity
EE Version 2.5.1

BoldMinded (Brian)

Aug 16, 2016

Hi Brian,

Hope you’re well! I have a question about adding a functionality to Wyvern.

Like the way a user can select Structure or Page entry right from the Wyvern modal, is there a way to do the same with regular channels? Is this something that is available with an existing add-on or something that can/needs to be developed separately?

Thanks!

Jae

#1

BoldMinded (Brian)

Yes, Wyvern makes variables such as {page_url:23} available anywhere, not just within the modal/custom field.

#2

Jay Barclay

Thanks for the quick answer. So, in the source code of a Wyvern field, would this work:

Test link

where 23 is the entry ID?

#3

Jay Barclay

Oops – forget to wrap it in code:

Test <a href="http://{page_url:23}">link</a>
#4

BoldMinded (Brian)

Yes, thats what the modal inserts when you click a Structure page.

#5

Jay Barclay

Hi Brian,

It works for a Structure page, but when I insert the same syntax that links to a non-Structure page, the it simply links back to self.

For example, on this page: https://www.theologyofwork.org/the-high-calling/newsletters/what-i-wish-my-pastor-knew-about-my-job-august-17-newsletter

I added a test link (since deleted) that has this syntax for the word “pastor”:

<a href="http://{page_url:10665}">pastor </a>

The result is that the link references self and not the entry ID 10665 (screenshots: https://cloudup.com/cQArhznHLdu)

Does this feature not work for non-Structure pages?

#6

BoldMinded (Brian)

It is only designed to work with Structure pages.

#7

Jay Barclay

Yup. That was my original inquiry – if the same {page_url:xyz} method worked for REGULAR (i.e., non-Structure) channels.

Would this be possible as a customization to Wyvern? If so, what would be the estimate?

Thanks!

#8

BoldMinded (Brian)

That wouldn’t be a Wyvern thing because it would need to look at the channel config to determine the path, and concatenate the path with the entry URL Title. Even then I’m not sure it’ll work in all cases b/c EE’s url structure is so loose.

If anything this sounds like a separate add-on, which I don’t have time to undertake. All my add-ons are currently in feature freeze b/c my focus is on Publisher for EE3.

#9

Jay Barclay

Got it. Thanks!

Login to reply