I have removed Wysiwyg Version 2! from some of my Sites and replaced it with ckeditor.

The wysiwyg folder is left there because some other installed sites could use it in an multisite environment.

And now i get some incompatibility Warnings about Wysiwyg and an advice to update it from 1.0 to 2.0, even when there is no version 1.0 on the whole server and all versions installed to the database are removed.

I couldn't find an explanation for this in the Database.

Comments

Look for another instance of the wysiwyg module in your modules directory...I've had this happen once before where I had accidentally copied a module to another modules directory. Then it took a while to find out that it was "hidden".

hope this helps

Category:bug» support
Status:Active» Fixed

Wysiwyg does not issue any warnings on its own about updating from one version or the other, and I don't think Ckeditor.module would do that either. The modules are incompatible and should only tell you that the other one needs to be uninstalled (patch in Wysiwyg's issue queue for that, now it just disables ckeditor.module on installation if enabled, which was considered bad UX.).

To see exactly where the active version of Wysiwyg lives, inspect the system table or run a query like:
SELECT filename FROM {system} WHERE name = 'wysiwyg';
Then remove that folder, flush your cache, uninstall wysiwyg if its tables are still there and you'll be fine.
Alternatively, remove the returned database row manually as well as any remaining {wysiwyg/wysiwyg_user} tables.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Status:Closed (fixed)» Active

Wysiwyg does not issue any warnings on its own about updating from one version or the other, and I don't think Ckeditor.module would do that either.

Did i say anything like that?

The modules are incompatible and should only tell you that the other one needs to be uninstalled (patch in Wysiwyg's issue queue for that, now it just disables ckeditor.module on installation if enabled, which was considered bad UX.).

Didn't i mentioned that i HAVE uninstalled Wysiwyg? It is in fact completely uninstalled on all sites that are affected!

To see exactly where the active version of Wysiwyg lives, inspect the system table or run a query like:
SELECT filename FROM {system} WHERE name = 'wysiwyg';
Then remove that folder, flush your cache, uninstall wysiwyg if its tables are still there and you'll be fine.
Alternatively, remove the returned database row manually as well as any remaining {wysiwyg/wysiwyg_user} tables.

My problem is that I have searched at this table and didn't find version 1.0 but version 2.2, as existing in the modules folder.

I will not remove the folder. As i said I'm working on an multi site.

Why is wysiwyg announced to me as version 1.0 which is considered incompatible? This is just strange to me.

Did i say anything like that?

That was in response to

And now i get some incompatibility Warnings about Wysiwyg and an advice to update it from 1.0 to 2.0

and was simply saying I don't know where the messages could be coming from since none of the modules you mention print such messages. You didn't state where the incompatibility warning and update advice were shown, nor what the exact messages were, so I can't be completely sure though.

The Ckeditor module does look to see if Wysiwyg is installed to inform you about conflicts, but won't advice you to upgrade it, which is why I tried to rule that module out as the culprit.

If the messages are on the status page, they're not put there by Wysywig, and I don't think Ckeditor module does that either. It could indicate some module is incorrectly detecting Wysiwyg as installed (or at least not being the version it expects). You did not mention changing any other modules recently, so I ruled this out. There's a slight possibility a module providing plugins for Wysiwyg could put the message there since it no longer detects the version it relies on. Then you need to find out which of your installed modules are providing plugins to Wysiwyg and reconfigure/remove/replace them as well.

If it's the regular message you get when looking at the list of modules in need of upgrades, then this is very likely the case where an old version of the module has [also] been installed somewhere, other than where you expect it to be. This is one of the few cases in which I can offer direct advice without more info, since it would require Drupal core to still have an entry in the system table for Wysiwyg, and it's easy to fix.

If the path returned by the SQL query on any of the affected sites is not in sites/all/modules/wysiwyg (unless you still have a few sites which do use their own version of Wysiwyg), you do still have an old version in that location. The version shown in the table might no longer match the version of the module files actually used, if an older version was accidentally dropped into a location which Drupal happens to scan before it gets to the correct version. The only sure way of knowing if that happend is to check the path in that table.
You could alter the record to point to the actual location of the module, if you do want to use Wysiwyg on that site, otherwise simply remove it. If you already did, but it shows up again after clearing the cache, the old Wysiwyg files are still there.

I will not remove the folder. As i said I'm working on an multi site.

I'm not suggesting you remove sites/all/modules/wysiwyg, I'm suggesting you remove any other folder pointed to by the path returned by the SQL query on the problematic sites. That could very well be a subfolder within sites/all/modules/wysiwyg, like sites/all/modules/wysiwyg/wysiwyg, if one accidentally extracted the module inside itself. Or it could be a subfolder within a different module, present on one or more sites, so make sure the paths match exactly. I have no way of knowing what your filesystem looks like, so I can only make certain guesses here.

Didn't i mentioned that i HAVE uninstalled Wysiwyg?

Yes, but you still getting messages strongly implies it's still installed. Core won't put up messages for uninstalled modules, and Wysiwyg itself can't once it's been deactivated. If it's a message printed by Core, the module is still installed in a location where it shouldn't be. If it's not from Core, another module has a dodgy detection check somewhere and there's not much I can do about that.

Thx for your advise TwoD.
The strangeness to me in this is more or less exactly what you have explained her :-)
I have already run the query:
Resulting in:
sites/all/modules/wysiwyg/wysiwyg.module
as only result.

Drupal is trowing this message out on
admin/reports/updates
and
admin/reports/updates/update

Where the message is:

Wysiwyg (not supported)
Installed Version 7.x-1.0

If you ask me, just the standard message by drupal core.

Ok, thanks for that info. I'm assuming that's the same result on all the sites in this multi site installation?

Yes, that's Drupal Core thinking the old version is still installed, and because there's no longer any 7.x-1.x releases available on drupal.org, it says it's no longer supported.

What are the contents of sites/all/modules/wysiwyg/wysiwyg.info?

cat wysiwyg.info

name = Wysiwyg
description = Allows to edit content with client-side editors.
package = User interface
;dependencies[] = libraries
;dependencies[] = ctools
;dependencies[] = debug
core = 7.x
configure = admin/config/content/wysiwyg
files[] = wysiwyg.module
files[] = tests/wysiwyg.test
; Information added by drupal.org packaging script on 2012-10-02
version = "7.x-2.2"
core = "7.x"
project = "wysiwyg"
datestamp = "1349213776"

Ok, thanks for that info. I'm assuming that's the same result on all the sites in this multi site installation?

This is actually the case on two different servers with multi sites.

If I activated wysiwyg module for testing. Even without deactivating ckeditor or anything else, the message in admin/reports/updates
and
admin/reports/updates/update
is gone!

I'm usually have enabled to check for updates for deactivated modules too.

Status:Active» Fixed

You say the message is gone now, so I assume something fixed it. Otherwise, please change the status back to active.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.