Using Context with the Delta module (Omega 7.x-3.1) to create a custom front page for a site I am developing. Uploaded the site from a local to a remote dev environment, then went to edit the conditions and reactions, and nothing happened. Nothing popped up on the right to edit. Then, all of a sudden, I lost all of my conditions and reactions, and could not recreate them! I tried disabling and installing a clean version of the module, still no luck. I finally solved it by aggregating the javascript files, but that behavior rattled me. Interestingly, Context is still working on the old local install, The problem occurred after I uploaded to the remote server.
Not sure its a bug, but wanted to point it out. Let me know if you need any more info on the install profile,
Comments
Comment #1
RKopacz commentedGiving this a nudge. Can anyone help me?
Comment #2
ShedPhotons commentedDepending on how your remote is set up, you may need to go through extra steps to get the entirety of your site ported to the dev server. With my host, everything under /files has to be hand-loaded. This could include your javascript files - when you aggregated them, had they already been uploaded?
Comment #3
RKopacz commentedThank you for the response. The entire site was uploaded in one upload via FTP to the server. Only the database parameters in settings.php were changed. With 6, I used to disable clean URLs and clear the caches before DB export and import, but have found with 7 I need to clear all the cache_tables by hand as well before export, or else the DB dump file will not import to the new DB. JS files were aggregated only after the upload, which, as I noted, seemed to temporarily solve the problem (incidentally, I find that I have to do this to get some drag and drop tables to work as well, post-upload to remote, particularly with menu items).
My next line of attack will be to examine the URLs to the JS files in the head and/or footer of the page. I suspect that they may not be correct for certain JS files, post upload.
Comment #4
RKopacz commentedNot sure if anyone is paying attention to this thread, but the problem persists.
I just moved a local dev site from a windows to an ubuntu install, moving from Wampserver on Windows Vista to XAMPP for linux 1.7.1 on Ubuntu 10.04. Same problem as before (no AJAX window when clicking on condition or reaction), then combined JS files in Dev > performance, and this time it did the kindness of delivering an error message, after I returned to the context admin:
Warning: file_get_contents(sites/all/modules/context(162)/plugins/context_reaction_block.js) [function.file-get-contents]: failed to open stream: No such file or directory in drupal_build_js_cache() (line 4841 of /opt/lampp/htdocs/.../includes/common.inc).
Don't know if this helps anyone, puzzled that no one else is reporting this. Does this duplicate an issue already in the queue? Didn't see anything in there before posting.
Hope somebody can help.
Comment #5
RKopacz commentedWell, it has happened again. Twice. Once I moved from one local dev to another. The only thing that got it to work was un-installing the module and re-installing it.
Now moved that same site to a remote production site. Trying disabling the module, re-enabling it, running update.php. Nothing. The only thing that works is aggregating the JS files under Performance. While I don't mind doing that, it seems that somewhere along the line there is a bug in this module.
I checked the way the scripts were loading in the head, and they seem fine. I counted two scripts. They both seemed to be OK.
Comment #6
emcniece commentedAre you logging any errors in your site reports? How about in your browser console? If you're using Chrome, hit F12 and click over to the "Console" tab, post what you see! Often there will be a javascript error of some sort.
Comment #7
zabej commentedCould you resolve the issue?
I have the same problem.
I've tried to use only cTools + Context but it was waste.
I use bluehost hosting.
Drupal 7.17 + Context 7.x-3.0-beta4 + CTools 7.x-1.2
Error console in FF retrieve
Error: TypeError: $.cookie is not a function
Resource: http:///misc/tabledrag.js?me9j99
Strings: 164
Comment #8
zabej commentedThis solution could help in my case:
http://drupal.org/node/1026640#comment-4173738