Errors generated on Upgrade to Alpha 1

same here:

    Warning: class_implements() [function.class-implements]: Class ImageCacheActionsModuleStreamWrapper does not exist and could not be loaded en file_get_stream_wrappers() (línea 136 de /home/mywebsite/public_html/includes/file.inc).
    Warning: in_array() [function.in-array]: Wrong datatype for second argument en file_get_stream_wrappers() (línea 136 de /home/mywebsite/public_html/includes/file.inc).

This indicates that you need to refresh the registry. A clear all caches should do so. I'm not sure that the array_merge warning also has this cause, but assume that it is due to the earlier errors.

Can you let me know if the error persists after clearing the registry cache?

I had similar messages today when doing some testing:

    Warning: Division by zero in theme_image_style_preview() (line 786 of modules\image\image.admin.inc).
    Warning: array_intersect_key(): Argument #1 is not an array in theme_image_style_preview() (line 788 of modules\image\image.admin.inc).

But this occurred with effects that failed to apply successfully. So I suspect it is a style/effect specific issue. Are you using custom actions? If so, you need to run update.php and please read the README.txt of the custom actions submodule about manual changes to the code you write.

If that does not help can you list the image style here, preferably as an array dump. you can create that using features.

This could very well be so. I have changed the way to specify files in a non backwards compatible way. You should now use:

either 1 of the enabled scheme's:
- public://
- private:// (preferred for site specific masks, overlay's etc that do not need to be shared publicly))
- module://{module_name}/{resource-name} (introduced by imagecache_actions module, and the reason for your first 2 warnings) ( preferred for module provided resources, like the button overlay of the mentioned module)
- temporary:// (unlikely to be useful, but supported anyway)

or a relative (to current directory, probably Drupal root) or absolute path.

I explicitly chose to do this in a non-backwards compatible way as there is now a multitude of possible locations (compared to only the public directory in D6) and there should be no confusion about what file will be taken from what location.

I did not yet have a look at the test suite. I'm afraid it is still mostly D6 based. We do have plans to set up a good test suite, as we also have plans for large refactorings. So a good test suite will be needed.

I will either remove it for 1.0 or have another look at it before 1.0. Thanks for reporting.

Created issue #1593246: Update to imagecache_actions 7.x-1.0 as a follow up to this issue.

code tags and non-warning text added

numbers

Unfortunately this issue is not fixed, I'm still getting errors 1 & 2 when updating from the 7.x-0.0 version to 7.x-1.0.
reopening for maintainer's attention.

As I see it, it is not an issue. You install the new version and before the new classes can be registered, they are already (attempted to be) instantiated (because registration and discovery work differently). So clear the registry cache and the error messages will be gone. If not, please re-reopen this issue, detailing again what messages you get and when.

Note that issue #1702716: System Stream Wrappers Conflict is kind of related and will resolve the issue in a next version.