Blocks
* warning: file_get_contents(http://fsd.monash.edu.au/misc/jquery.js) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in /net/www/fsd/sites/all/modules/javascript_aggregator/javascript_aggregator.module on line 33.
* warning: file_get_contents(http://fsd.monash.edu.au/misc/drupal.js) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in /net/www/fsd/sites/all/modules/javascript_aggregator/javascript_aggregator.module on line 33.
* warning: file_get_contents(http://fsd.monash.edu.au/sites/all/modules/admin_menu/admin_menu.js) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in /net/www/fsd/sites/all/modules/javascript_aggregator/javascript_aggregator.module on line 33.
* warning: file_get_contents(http://fsd.monash.edu.au/sites/all/modules/devel/devel.js) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in /net/www/fsd/sites/all/modules/javascript_aggregator/javascript_aggregator.module on line 33.
* The selected file /tmp/filevAlhTs could not be uploaded, because the destination js/9f8e0962d720473d59e5b50fb8287657.js is not properly configured.
Comments
Comment #1
realityloop commentedUpdate - Some of the errors were due to me tricking via hosts.. the real error is as follows:
List Blocks
The selected file /tmp/filetCcjHu could not be uploaded, because the destination js/9f8e0962d720473d59e5b50fb8287657.js is not properly configured.
Add Block
The selected file /tmp/filePIDBLe could not be uploaded, because the destination js/9f8e0962d720473d59e5b50fb8287657.js is not properly configured.
Comment #2
derjochenmeyer commentedThanks, for the feedback. I'll take a look. It seems the files/js folder is not properly created in some environments.
Comment #3
derjochenmeyer commentedDoes the Drupal built in CSS aggregation work for you (admin/settings/performance)?
Do you get a similar error?
You can also try this "patch" (http://drupal.org/node/211162).
Comment #4
derjochenmeyer commentedI made some changes regarding how the module processes the .js files. Try the new release. Its has new features and a settings page under admin/settings/performance.
Comment #5
realityloop commentedNot getting the errors anymore, which is good.
However, with the module enabled it triggers Mr. Uptime extension (http://mruptime.pingdom.com/) on every page load which I would think is probably a bad sign.
Comment #6
derjochenmeyer commentedHm, what do you mean by it gets triggerd? I installed Mr. Uptime, but i dont see any action going on when visiting a site with js cache.
Does Drupal6 js aggregation cause the same problems? I guess Mr. Uptime will have to fix his Plugin soon ;-)
Comment #7
realityloop commentedyou may need to enable the following setting in Mr. Uptime:
On server error pages:
-Open Mr Uptime toolbar
That said.. it may well be an issue with the extension and not with your module, I don't have D6 installed anywhere to check.
Comment #8
derjochenmeyer commentedCannot reproduce the error. I checked with Mr. Uptime 0.9.2 on several pages with .js cache enabled.
(On server error pages: "Open Mr Uptime toolbar" is checked)
Comment #9
derjochenmeyer commentedMarking it as fixed because the original problem was solved.
Comment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.