Bad link tag ` since 2.5.5

That's some pretty deep nesting. If I'm reading it right, you have (at the least) a link tag inside a chunk inside a pdoMenu tag inside a pdoResources tag.

Your inner pdoMenu tag doesn't have a property set, and it won't have access to the property set of the outer pdoResources tag, so it can't set the link tag.

Adding the property set to the inner pdoResources tag, could possibly work, but I wouldn't put a lot of money on it.

Ironically, I'm now getting this error after updating to 2.5.7.

Mine says:
ERROR in resource 282 etc.

That's my blog container.

Is resource 79 your blog container, by any chance?

Has anybody found a solution for this bug yet? My error log is flooded by these [[~]]-stuff, too.
I tried to nail the cause down by removing code part by part but somehow it's like a ghost. I cannot get a hold on it. It behaves very strange.

I'm now getting these on a few other recent blog articles, but so far not any other pages. Are you using Articles, and are the resources listed in the error messages all blog articles?

I've looked at the specified Resources in the database and I don't see anything different about them. It could be a link tag parsing issue, which would make it very difficult to track down.

I have similar problems but I don't know if it's connected with some opcache issues or modx. I have a test site and I manually added pages into menu using [[~3]] ect.. Text in href shows up but link is not created and I get an error



After I clear opcache and modx cache link is created and error doesn't appear anymore.

UPDATE:
I added: "php_flag opcache.enable Off" to my .htaccess file and I never got that error again. So in my case opcache caused me problems.

I tested this on fresh 2.5.7 installation

[ed. note: theuros last edited this post 6 years, 10 months ago.]

@theuros Here's something to try:

Remove that line from .htaccess.

Create a resources called ClearOpCache with this content:



Then create a snippet called ClearOpCache with this code:



Then view the ClearOpCache resource whenever you make changes to anything with a link in it.

If it works, it should speed up page loads.

Well, I created a cc.php file on root wich I use to clear it, but putting into modx make more sense

I'm thinking to create a plugin to clear opcache when I clear modx cache and maybe on document save or some other appropriate system event.

I was thinking of something similar, though I imagined an extra that just added a top-menu button. A JS handler could make an AJAX call to your file and pop-up a success message (or not, depending on a System Setting). That would let you do it only when necessary.

A much easier alternative would be to just have the top-menu button forward you to the resource I described above, but that would take you away from where you are in the Manager.

This is fired by every (?) pages.
2 contexts for 2 languages.

Just updated to 2.5.6, but his does not change anything for the error log issue.
I read this: http://ankur.com.bd
and contasted the correction of line 315 of online shopping bd
to 2.5.6 update.
I ran the W3C dead link search on one of our site's page (one listed in the error log) and no dead link was found
so... wtf ?

Ya'll have Tagger installed and running?