As a SO/CE, I want to know about potential path conflicts with F5 routing about express HOT 8 CLOSED

Atlas query is where={"pool":"WWWLegacy"}

from express.

@kreynen Does this only apply to prod? I installed a site on dev and created a TEST node which didn't seem to recreate the issue: http://www-dev.colorado.edu/p1aed93ac240/test

from express.

It applies to all environments, the list of conflicts varies by env

from express.

Something to be noted here: I've attempted to use hook_node_validate() to prevent a user from creating a node that conflicts with F5 routing but there's no way to get the pathauto generated path at that point. We may at best be able to emulate the behavior by copying and altering the pathauto_create_alias() function but that seems somewhat hacky. As an alternative, we can, however, check the path at hook_node_insert() and then set a warning message that the freshly created node path is a conflict.

One last thought is, using a hook_update_N(), we could populate the table of paths that are checked against for unique URLs (menu_router?) with the legacy paths so when a new node is created it'll either auto-create a unique URL or throw a message if manually attempting to enter the path.

from express.

Moved this issue to the express_homepage repo since that's where the code is. See CuBoulder/custom_homepage_bundle#137

from express.

Could maybe test with a text file containing JSON of paths.

from express.

Related #1886

from express.

The f5 is being deprecated so this is no longer relevant.

from express.