Andrew.Macpherson → created an issue.
Andrew.Macpherson → created an issue.
Andrew.Macpherson → created an issue.
Hi Valic, thanks so much for the quick fix! :-)
Andrew.Macpherson → created an issue.
Not sure if I should be posting here or not, but I have tested a few sites, and I can't actually see any option to VIEW any revision. That is, I can use the action buttons to either revert to or delete any revision listed, but I can't actually see the revision content itself. The 'view' link that is on the node revision interface is not appearing.
Andrew.Macpherson → created an issue.
Hello again! Actually, I worked out how to translate the 'before' and 'after' strings, by overriding the module template with |trans … but how do I translate the 'Join Word'? Thanks!
Andrew.Macpherson → created an issue.
Andrew.Macpherson → created an issue.
Andrew.Macpherson → created an issue.
Thanks, Adil, for the quick reply and for clearing things up.
It's good to know that this issue has a solution, but I'm never really comfortable going with dev releases unless absolutely necessary. Since I had already come up with a workaround of sorts, I will probably first wait a while to see if a new alpha, beta or stable release comes out.
Thanks again, Andrew
Andrew.Macpherson → created an issue.
Can I just check that you're considering one absolutely essential use case, please?
The media library contains documents as well as images. When we link to a media document container (whether in a field reference or in CKEditor), we need to have the path resolve to the file itself rather than the media entity. So that when we link to a PDF that's in the media library, for instance, the browser displays (or optionally downloads) that PDF.
If made from CKEditor, that link must also be a normal inline element.
The second requirement, which follows naturally from the first, is that if we replace the file in the media container (with an updated version of the PDF, for instance), any existing links then resolve to that updated version.
I hope I explained that well enough because it really is an absolutely critical need!
Thanks, Andrew
Hi Mark, I'm not sure if Linkit should be marked as deprecated, although I admit I may not fully understand what that implies. If I correctly (even though quickly) read the discussion about the improvements in Drupal core, they're not thinking about a full-featured replacement and there are several really important use cases where the proposed solution seems to be to "use the contrib Linkit module". So it seems they might be thinking that the two will sit alongside each other, perhaps?
Okay, no problem. I'm happy to wait for a version 4 release.
So please feel free to close this ticket.
Thanks so much!
Hi Lee, and sorry, my mistake.
I didn't mean to post against the 4.x-dev branch!!
I'm actually using the current Entity Hierarchy 3.3.4 …
Andrew.Macpherson → created an issue.
Andrew.Macpherson → created an issue.
Andrew.Macpherson → created an issue. See original summary → .
Thanks so much; I've updated and things are working just fine now!
Apologies for not being quite tech-savvy enough to handle patches and stuff.
I'll find out how to do that kind of thing …
Cheers, Andrew
Thanks, everyone, for your work on this fix!
I think I ran into this problem just now after going to use price lists.
But (please forgive my ignorance), what's the next step?
When and how will this be moved to a formal release?
Thanks, Andrew
Andrew.Macpherson → created an issue.
New maintainers would be wonderful, but I'm afraid I can be of no help at all with this: I simply don't have the skills/knowledge.
I agree that this is an exceptional module … in fact, I've often wished they would move it to core (although I also appreciate there may be good reasons why that shouldn't happen). I reckon there are probably a lot of sites that are waiting for this module to be made compatible with Drupal 10 so they can upgrade