So we are basically at beta stage now. Feature set has been frozen unless you have a pretty good idea that's quick to implement.

Lots of testing is needed. I'd like to state that the core function (inserting code, and the bit that returns the correct image hasn't really changed since I first coded them, so it's a pretty safe module to run. The only issues are UI issues since ImageBrowser is simply some sexy glue that strings some modules together and makes it easy for users to use.

Areas I need help testing:
- Upload errors, sometimes upload never happen and get stuck on the AJAX whirl. Please try and help narrow down the parameters needed to make this error happen.
- Sometimes Drupal messages don't get logged by the JS log manager, might be related to the above issue, but testing is needed.
- Try some funky View filters and see if all is OK.

Issues I know about:
- If you edit an image and replace the image with a new one then the edit and browse windows still hold the old cached version of that image. Need to look into making sure that doesn't happen.

We are very close to an RC and a stable release so keep up the good work guys :)

Comments

laceiba’s picture

laceiba commented

If you edit an image and replace the image with a new one then the edit and browse windows still hold the old cached version of that image. Need to look into making sure that doesn't happen.

I also found that when I added a new image size, Image Browser does not recognize it. The new image exists and was regenerated by the image module, but I can't select the image through the interface. Great little piece of code, however. I like the way you set this up.

jdelaune’s picture

jdelaune commented

Have you enabled the correct permissions to use the new preset?

laceiba’s picture

laceiba commented

I will take a look at that. It's possible that is my problem.

jdelaune’s picture

jdelaune commented
Status: Active » Closed (fixed)