Describe your issue or idea
This is a follow-up to #2842 where we realized that a lot of people were upgrading from Drupal to Backdrop in a way that will result in broken sites.
The root of the problem, it seems, is that people want to update core before contrib, and contrib modules often require their updates to be run between two core updates.
One way we might mitigate this problem is to at least let people know that some modules might be missing by setting a warning at the top of the update page. We could check for missing modules by:
* Check the system table for all modules. Check the modules location(s) to see which modules are present. Compare the two.
* Check if there are tables in the database which are not defined by a hook_schema.
GitHub Issue #:
2853
Recent comments
That function also exists in Backdrop so it might be something else going on. https://github.com/search?q=repo%3Abackdrop%2Fbackdrop%20image_gd_create...
imagecolorsforindex(): Argument #2 ($color) is out of range
I did some searching and learned that this is a known problem with some GIF images. The Drupal 7 api docs show that there is additional code in image_gd_create_tmp.inc to check for this case and...
imagecolorsforindex(): Argument #2 ($color) is out of range
@Coffee70 Thank your for the further clarification. I just wasn't clear if you used the modules in the backdrop-contrib repos or rolled your own through coder_upgrade. With your experience I am...
Customizable newsletter