Conflict between Cachelite and URL Router about cachelite HOT 13 CLOSED

@vlad-ghita that's a good spot there, can you confirm this?

from cachelite.

I stumbled on it already. Yes, I can confirm this.

from cachelite.

If anyone knows how to achieve this, can you pick it up please?

from cachelite.

Quick fix:

Uninstall Cachelite.
Install Cachelite.

Hopefully, it will get the highest ID in tbl_extensions table and thus fire latest (after URL Router).

Though I think Sym 2.3 executes extension delegates alphabetically in Extenion order ... sucks :(

Ideal option ... custom delegate execution order editable in Admin ;;)

from cachelite.

Maybe @brendo can shed some light on how we could do this?

from cachelite.

Agreed, CacheLite should be updated so that it waits for the page to be properly resolved first.

from cachelite.

Would anyone like to take charge of this?

from cachelite.

Depends on how fast you need it. I would do it, but could take a few days before I actually get to do it.

from cachelite.

There's no urgency, just a need to take ownership of the update.

Really appreciate it Jens.

from cachelite.

While there is no way to currently make Cachelite execute before URL Router (see #993), I think this issue can be solved by using the information that is passed via the delegate instead of using the $_GET array.

The FrontendPageResolved delegate passes back the page_data of the resolved page, which contains the current page path which looks like it may simplify the logic of that _in_excluded_pages() function.

from cachelite.

@brendo Thanks. Will try that.

from cachelite.

@jensscherbl

Any updates on this?

from cachelite.

Will push an update next week, sorry for the delay.

from cachelite.