If our client selects a structure managed page from the Wygwam link tool, the URL doesn't always parse, resulting in the occasional {page_XX} instead of the full URL. However if I drag the page that is getting link to around in the Structure tree, and place it back to where it belong the URL is updated.

I suspect this might have something to do with the Transcribe+Structure combination, as there are still a few small bugs here and there with that collaboration, but I can't tell for sure.

I'm on EE 2.5.5, Structure 3.3.8 and Wygwam 2.7

Any ideas?

  • Hey Magnusland - what versions of EE and all of those add-ons are you on? Can you add that to the original post? Also, if you open your browser's debug console, do you see any JS errors? – Lisa Apr 30 '13 at 15:23
  • Hi @LisaWess, I've added this now. – Magnusland May 6 '13 at 8:49
  • And no JS errors in the console. – Magnusland May 6 '13 at 9:00
  • Magnusland - is you take transcribe out of the picture, does this still occur? Isolating where the issue is would help quite a lot. Also, are you saving the entry while Wygwam is in its normal mode, or is it in source mode? Thank you! – Lisa May 6 '13 at 17:00
  • If the problem occurs when you try and reference a page from one language in a Wygwam field of a page in another language then it is probably Transcribe related. It has to do with how Transcribe overrides the site_pages data . If you dump out $pages['uri'] in _get_pages_mod_data method of the Wygwam_helper class you will see the issue when you search for the entry_id (page_{entry_id}) in the array. What complicates fixing this is Transcribe also jacks up the urls in the site_pages array too. :( I am working on a fix, but it doesn't look promising at the moment. – th3mus1cman Jul 3 '14 at 18:05

I can say that it doesn't relate to Transcribe. I have a site where randomly some (but not all) the links set with the Wygwam Structure link browser outputs {page_XX} like you are describing. We are not using Transcribe.

I am also on EE 2.5.5, I was on Structure 3.3.8 (now on 3.3.10), and Wygwam 2.7 (now 2.7.1).

I'm not really sure if the upgrade to Structure or Wygwam has fixed the issue. I don't have a way to reliably reproduce it. But I have seen the issue, and am also concerned.

Hopefully that helps figure things out.

  • James, if you see this crop up again, can you let me know? Leaving it in its broken state may also help. Also, could you try the modification here: expressionengine.stackexchange.com/questions/9631/… and see if it helps? – Lisa May 28 '13 at 21:08
  • I'll keep a look out for sure. I can't say they'd be too thrilled for me to keep it in the broken state... but perhaps I can do a DB dump of that cell. I did see the modification in that other post. I was actually the one that responded. I'm a little hesitant though to hack the module and would prefer of course an official fix. I just don't want to introduce potentially more issues by using the hack. – James May 29 '13 at 17:48
  • That hack is temporary, it is reported as a bug so we'll get an official fix out there. You can always back up your files to roll back the hack if it doesn't work; it should not impact upgrades though. And yes,a db dump in the broken state would be good. :) – Lisa May 29 '13 at 18:07
  • ok, I found an example with both the Structure page link not resolving and an Asset linked image not resolving. Where should I send it to? – James May 31 '13 at 18:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.