As stated in the release notes on http://drupal.org/node/207756 do not use 1.6! Use 1.7 instead. But where is 1.7?
I have had much problems with images when updating from 1.5 to 1.6: all nodes containing images via image_attach or image_assist didn't load anymore (blank pages) argh....
By moving all modules in sites all modules in a different directory and than moving them back one by one I found out that nodewords was the module that did the shit (in a quick and fresh installation with image and nodewords no problems occured). As I upgraded image, too, I thought image had to be downgraded and so I did. But the result was the same. After some hours testing I looked for other releases of nodewords and found this silly statement: do not use it! But why has it been published then? If I downgrade nodewords the update status always claims that there are new versions to install.
So please, remove 1.6 from the release list!
Comments
Comment #1
adale commentedYes, where is 1.7? We need it as long as it fixes the problem created by 1.6.
Comment #2
ashtronaut commentedwow, I just realized the issue after installing to my dev site. Anybody find 1.7 yet?
Comment #3
tormiTry this to fix 1.6 error: http://drupal.org/node/208244#comment-685875
Comment #4
Robrecht Jacques commentedHmm, strange. 1.7 is here but the main page doesn't show that as the latest version ??
Comment #5
Robrecht Jacques commentedWorking on it... Seems I didn't follow correct procedures...
Comment #6
Robrecht Jacques commentedOK, got the 1.6 release unpublished. Something I couldn't do by myself...
I hope to get 1.7 out soon.
Comment #7
ElSanto commentedI did change, but I still leaving some white pages in the book in particularAfter making changes, I found that remained white pages, and I realized that it was caused by the module codefilter
Comment #8
tormiWell, 1.7 is available now, but it's not recommended according to /admin/logs/updates. Recommended version is 1.5. The status of 1.7 needs to be updated to the "recommended version" at drupal.org.
Comment #9
Robrecht Jacques commentedComment #10
pepe roni commentedThanks!
Now it works (for me)!
Comment #11
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.