Installing Textile in 4.3.2 stops kills Modules admin screen before even enabled
| Project: | Textile |
| Version: | 4.3.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | jhriggs |
| Status: | closed |
Jump to:
I installed textile as described in its INSTALL file and then tried to navigate to: http://myurl.com/admin/system/modules and found a mostly blank page (no modules listed at all, view html shows the source cut short when starting to fill the main page).
If I remove the (just created) modules/textile directory and its contents, then the module select page comes up as expected.
Note that I haven't even enabled textile at this point. Just untar'd the files into the directory. I also switched to the standard Marvin theme just to be sure it wasn't a hacked theme problem.
I'm happy to help debug this - just tell me where to start! (I checked the drupal error log but didn't see anything there).
thanks! (Really looking forward to getting this module going!)
#1
I tried this with an even more stripped down version of 4.3.2 but with the same result. Also, I realized that I was mistakenly putting the textile files in a subdir of modules/, but correcting that made no difference.
Does anyone else have textile working 4.3.2?
thx, michael
#2
Actually, putting it in a subdir of modules/ is correct. You should have all the files in modules/textile/. I cannot reproduce this problem. I am using this module in 4.3.2 with no problems. Is there a conflict with some other module? What other contrib modules are installed? You are using the 4.3 version of the module, not CVS, correct?
#3
Closing due to inactivity.