I get :

Install version 3.2.8 of the Supersized (from <a href="https://github.com/f3ndot/supersized/tree/3718ae83f0945e327cc09530b959c5a8b049871f">here</a>) in a libraries directory such as "sites/all/libraries."

But where is 3.2.8 ? ON https://github.com/f3ndot/supersized I only can get 3.2.7

Comments

ahlofan’s picture

If you need to know where is it, it is here
https://github.com/f3ndot/supersized/tree/3718ae83f0945e327cc09530b959c5...

Just follow the instruction, download it, decompressed it, and place the whole folder into your libraries, you don't have to worry anything else.

Hope it helps.

guillaumeduveau’s picture

Category: Bug report » Support request
Status: Active » Fixed

Thank you, it works now. In fact I had everything fine, except I installed the module before installing the folder in sites/all/libraries. Just had to deactivate supersized context and reenable it.

Status: Fixed » Closed (fixed)

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

knalstaaf’s picture

It's not that innocent I believe.

I had the same problem, without the context submodule enabled. Switching on and off the (main) module didn't help.

I had the library installed from the official Supersized library (it's a natural reflex to do so), and got the message as mentionned in the OP, while the status report stated it was all ok - very confusing.

Turned out I couldn't disable the module eventhough the Supersized field was deleted and at a certain point I deleted the whole content type to make sure. Ran cron, emptied caches, nothing, couldn't disable it.

Took a look at the DB, saw two fields that seemed suspicious to me: field_deleted_data_23 and field_revision_data_23. I removed them, went back to the modules; still not possible to disable the module (ran cron, emptied cache). I'm not sure if they're related to the Supersized module though.

Then it turned even more grim: after deleting the Supersized field (of a re-created content type with a different machine name), I got this:

PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'useraq.field_deleted_data_23' doesn't exist: SELECT DISTINCT field_deleted_data_230.entity_type AS entity_type, field_deleted_data_230.entity_id AS entity_id, field_deleted_data_230.revision_id AS revision_id, field_deleted_data_230.bundle AS bundle FROM {field_deleted_data_23} field_deleted_data_230 WHERE (field_deleted_data_230.deleted = :db_condition_placeholder_0) AND (field_deleted_data_230.bundle = :db_condition_placeholder_1) LIMIT 10 OFFSET 0; Array ( [:db_condition_placeholder_0] => 1 [:db_condition_placeholder_1] => inspiratie_ss ) in field_sql_storage_field_storage_query() (line 652 of modules/field/modules/field_sql_storage/field_sql_storage.module).

Fortunately I took a backup before venturing in this issue. Though it wasn't the end of my cavalry.

After deleting another new Supersized field of a new content type, I got this again:

DatabaseSchemaObjectExistsException: Can't rename field_data_field_sliss to field_deleted_data_24: table field_deleted_data_24 already exists. in DatabaseSchema_mysql->renameTable() (line 307 of www/includes/database/mysql/schema.inc).

After restoring the backup once again, ànd running cron, emptying caches if you will, I could finally disable it. I de-installed it as well, and started over with the library files downloaded from the source mentioned above.

Same thing happened all over.

After another restore of the database, disabling and deinstalling the module, I noticed fields like field_deleted_data_24 and field_revision_data_24 were still in there. I left them there just to make sure not get into trouble again - since these are most definitly related to core.

  • D7.39
  • Supersized 7.x-1.5
  • jQuery 1.10
  • Supersized 3.2.8 installed.

Maybe the status report should mention when the correct library is not being used with a link to the right one (the one mentionned on the project page), if that's the cause that is.

I've used this module before, with no issues at all. I have no idea what got so terribly wrong this time…