I tried to update the module to 5.0, wrote the .info file, made some fix according to the new settings page handling, but whatever I did, the module did not show up in the modules page. I spent a day trying to fix the problem, and supprisingly the solution is:

The module name should be changed to something other than inline, for example inlin.module and inlin.info will do.

I guess this is because 'inline' is somehow used in php or drupal for controlling and escaped.

Comments

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Project: Inline » Drupal core
Version: 6.x-2.x-dev » x.y.z
Component: Code » base system

@Drupal core team:
What is this about? pentike describes that inline.module's tags [inline(.*)] won't work in Drupal 5.0 anymore...? Is this true? If so, why? This would have a major effect on Inline API (currently in conceptual draft phase).

Don't know if this belongs to base system or filter.module. Please move this issue back to project Inline after clarification.

heine’s picture

heine commented
Status: Active » Closed (duplicate)

Pentike describes that the module when named inline.module doesn't show up in admin/settings/modules.

Duplicate of http://drupal.org/node/83565

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Project: Drupal core » Inline
Version: x.y.z » 6.x-2.x-dev
Component: base system » Code
Priority: Critical » Normal

Moving this issue back to Inline.

pentike’s picture

pentike commented
Status: Closed (duplicate) » Closed (fixed)

Looks like there was something with my cvs revision only. With the current HEAD it's working.