Hello,
on nodes that contain a supersized image, the SEVEN theme displays the supersized background image and makes it difficult to manage WHEN EDITING.
How is is possible to avoid this problem ?
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | context_settings.png | 54.21 KB | maxplus |
| #10 | node_edit.png | 999.75 KB | maxplus |
Comments
Comment #1
ahlofan commentedat the moment, you could use Context to avoid Supersized.
Comment #2
webmestre commentedPerhaps, but how ?
Comment #3
ahlofan commentedhi webmestre, I'm very sorry I made a mistake. You are right, currently this module is not providing any way to disable Supersized. Please allow a little time for a little thought of how to best implement this. I will push this feature to the latest dev version within days, and make sure to keep this issue update.
Comment #4
webmestre commentedHello ahlofan,
thanks to think on a way to fix this problem.
Comment #5
maxplus commentedHi,
I tried to install the current dev version of june 7th but I still get the supersized background on node edit.
Is it already implemented in the dev version?
Great module by the way, so easy to install and configure => THANKS!
Comment #6
ahlofan commentedhey guys, I'm so sorry that due to my really busy day time job, I'm still working on this. But it will be soon. I'm creating another context reaction that actually disable Supersized. In this case, it will be so much more flexible, you could use any condition to disable Supersized. For example:
Condition:
Path -> node/*/edit
Condition:
Disable Supersized
Comment #7
ahlofan commentedHey guys, tried pushed the latest snapshot to dev. You may download and try it. I added a new context reaction, "Supersized (Disable)". You may disable Supersized in any condition such as Path -> node/*/*. Please let me know if any problem found.
* Latest snapshot won't popup right away, make sure it is on June 14, or later.
cheers, and have fun!
Comment #8
webmestre commentedHello,
the new context reaction, "Supersized (Disable)" only appears in the reactions list after flushing all caches. OK.
BUT it has no effect neither with node/*/* nor node/*/edit path condition.
No effect when giving a real path (i.e. node/4/edit)
Comment #9
ahlofan commentedI have tested that again, seems no problem. Any other having the same problem?
a snapshot of the logic of context in supersized.moudle line 381
You can see that if 'supersized_disable_context' is found and return TRUE, nothing will happen at all by 'return;'.
Can I have more details on your context settings? Maybe an export?
Comment #10
maxplus commentedHi,
thanks for the effort but I have the same problem.
I can add the context to disable Supersized on node/*/edit is doesn't get disabled.
Now I have tested it on one specific node (node/122) but that didn't make any difference.
Below you can see my context export and some screenshots.
I'm using your current dev version of Supersized of june 14th and I tried Context 3.0 beta 6 and also the current dev version of april 28th.
Comment #11
ahlofan commentedThanks for the info maxplus! And apologise to whoever tested the dev. I know this will piss you guys off, but I have to tell the truth. I did NOT push the Context checking changes to GIT, and have just done it a minute ago. Please download the latest dev again when you see it updated. (>= June 18th)
Comment #12
kvoltz commentedI can confirm that the new dev version works as designed.
Fantastic module ahlofan!
I used to install supersized with a nasty combination of custom themed views, and hacked JS.
I really appreciate the module and the time it saves me.
Comment #13
maxplus commentedYES,
I can confirm that the dev version of june 18th works perfect on disabling Supersized on any Context condition.
Thanks, keep up the great work!
Comment #14
ahlofan commentedThanks everyone. Since this is confirmed by 2 persons, I will release this feature with some little bug fixes.
Comment #15
webmestre commentedHello ahlofan,
the new release works perfectly.
Congratulations and thanks for your very good module !!!
Comment #15.0
webmestre commentedadd "when editing"