Error message when using Drupal 7.50

Thank you for contribution. Please allow some delay on this.

Just a tiny review, could you please make it ternary operator?
$slick_fields = module_exists('slick_fields') ? url(drupal_get_path('module', 'slick_fields') . '/README.txt') : '';
Thanks.

Thank you.

The far below module_exists() parts can use the above defined variable parts, but that's okay.
Please allow some delay to get back on this.

Patch in #7 clears up the error messages for me (on 7.x-2.0). Thanks @PhilY!

There was already a commit for that file. Perhaps next time should patch against DEV. But that's okay, yours brings it back correctly anyway ;)

Committed with a little change. Thank you for contribution.

I installed patch, some errors disappear but I have still one:

User warning: The following module is missing from the file system: variable. In order to fix this, put the module back in its original location. For more information, see the documentation page. w _drupal_trigger_error_with_delayed_logging() (linia 1229 z /home/vidicon/ftp/brodnica/includes/bootstrap.inc).

Slick view and Drupal 7.50 new issue

Most issues with these are triggered by improper call to drupal_get_path(), drupal_get_filename() or similar functions.
Or when modules are not uninstalled properly. See more info here.

The patch fixed this for Slick.

Slick don't use variable.module, so it has nothing to do with Slick anymore.

If you always do clean uninstall, the other possible reasons on your case:

• There is another module that does the same mistake. Please check out any module that does depend on variable.module, and see their issue queues for solution. See /admin/modules for quick review.
• If you do custom coding via custom module or theme, you may want to re-check those functions, and add proper check prior to calling them. Normally cleared out like what the patch did.

You should be good when the culprit found.

It's great that this was resolved. Can we expect a new proper version pushed any time soon? Getting slightly annoyed by the error messages and can't be arsed to manually fix it on a couple dozen sites. Cheers.

Not soon, I am afraid. But you can patch, or copy/paste the entire function into the stable version.

I may be able to arrange alphas or betas prior to another stable full release, but not soon ;)

Hang on, there.

It is slick_ui.module is the culprit.

It is already mentioned in the project that Slick UI "can be uninstalled at production."
I myself always uninstall it at productions.

Now I recommend it ;)

You are safe even to remove it after uninstalling.

Had similar challenges in the sassy module related to changes between Drupal core 7.44 and Drupal core 7.50 , passing a name of a module that is not a module name to the core api causes errors /warnings that previously were ignored. I had to commit a workaround to the contrib module in order to make the simpletest tests pass on jenkins.