The FeedBurner module executes drupal_bootstrap(DRUPAL_BOOTSTRAP_PATH) inside of feedburner_boot(). This causes the parsing of the URL including activation of custom_url_rewrite_inbound. FeedBurner sets its weight to -1 so it is invoked prior to subpath_alias which has the default weight of 0. As a result subpath_alias_url_inbound_alter is not defined and will not be executed by url_alter. Fixing this on subpath_alias requires adding an install file to set the weight to less than the weight of the FeedBurner weight of -1.

Comments

Dave Reid’s picture

Dave Reid
he/him
Primary language English
Location Nebraska USA
CreditAttribution: Dave Reid commented

Subscribing...entirely possible that I'm going to depend on URL alter completely in FeedBurner instead of definining custom_url_rewrite_outbound

GerdC’s picture

GerdC CreditAttribution: GerdC commented

Subscribing... see also bug http://drupal.org/node/921686

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
CreditAttribution: klonos commented

I know this is off-topic here, but since Dave joined in this conversation I need to ask this:

Has anyone thought of a way to have module weights adjusted in a central way as issues such as this one arise? There could be a contrib or even better core module that would take care of exactly that. Each module-weight-related issue would be an issue in that module's queue and with each new version/update of the module a list of known issues with certain modules would be addressed. In other worlds I am talking about a central database that would hold module weights and would make sure that these are being updated each time an issue comes up.

If that came to be, and there were known issues caused by the 'timing' of a module is called to act, all their module developer(s) would have to do would be to simply request their module to be included in the weight database before module x and after module y. What do you people think? Should I file this as a core request?

[aware I'm risking a 'care to code this?' reply here, but I sadly cannot, so throwing an idea here]