I just upgraded my Magento site from 1.6 to 1.8.1. After the update the website is unable to load CSS and JS. I checked the error log and it says this:
[Tue Apr 22 16:40:30.616082 2014] [core:crit] [pid 27847:tid 140041728800512] (13)Permission denied: [client 60.240.167.112:59507] AH00529: /home/strictly/public_html/js/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable and that '/home/strictly/public_html/js/' is executable,
I followed many people's advice and did these:
Clear cache in var/cache folder
web/unsecure/base_url and web/secure/base_url configurations are correct (they both point to the corrent URL)
dev/js/merge_files and dev/css/merge_css_files are both 0
Even after this the site loads very slowly, and when it loads it's not no CSS and JS. I check the behind-workings using Chrome's Inspect Elements button and I can see the CSS and JS files failing to load, each giving 404 not found error.
My guess is it has something to do with setting the correct permission for the JS and CSS folders/files. Does anyone know how I could do this?
Thank you
Found an answer.. I had to set the permission of skins folder to 755. After this, everything started working :)
Related
After adding Content module to a page, I just get a round blue icon with white glasses. Clicking on it produces an error in the console:
ReferenceError: $2sxc is not defined 1 ui.html:20:5
<anonymous> http://localhost/DotNetNuke/desktopmodules/tosic_sexycontent/dist/ng/ui.html:20:5
Clicking 'Change Template / Layout' in pencil menu also does nothing. This happened after upgrading from 2sxc 8.12 to 9.02. I checked the file and of course could not see $2sxc defined anywhere. I have installed on other sites and not had this problem, but it is failing on my localhost installation. DNN 9.1.1 I have tried uninstalling 2sxc and deleting all the Tosic... files I can find, then reinstalling, but I get the same results.
Similar to: Having some issues with 2sxc version 9.x: unable to select App/Content layout
Does anyone know how to fix this? Thx.
I fixed this after a little debugging and following the code. The problem happens on localhost implementations. There is a file: DesktopModules\ToSIC_SexyContent\dist\ng\ui.html
that contains the code in a script container:
var
path = window.location.pathname,
isDevMode = window.location.hostname === 'localhost',
apiUrl;
The problem is that it thinks it is in 'DevMode' when it is on localhost and therefore sets:
devPath = 'http://2sxc.dev/desktopmodules/tosic_sexycontent/dist/a4/';
which is certainly not a valid URL on my system, and apparently not on the web either. So the solution is to have it avoid 'DevMode' and everything works as it should. I did this by modifying the 'localhost' to be 'xlocalhost' and it worked like a charm. You could also just set it to false.
So this was a bug in that version, it's fixed now.
I have to set up the cache on a WordPress project, which is already on "support mode" in the agency for a while.
The plugin WP Super Cache was already installed so I activated it, to setting up it.
I work locally on dev mode and the project have a preprod and a prod environments.
When I activated it, the following error messages appear in back-office :
Warning:
include(/var/www/xx/xx/xx/xx/xx/xx/wp-content/plugins/wp-super-cache/wp-cache-base.php):
failed to open stream: No such file or directory in
/var/www/wp-content/plugins/wp-super-cache/wp-cache.php on line 65
Warning: include(): Failed opening
‘/var/www/xx/xx/xx/xx/xx/xx/wp-content/plugins/wp-super-cache/wp-cache-base.php’
for inclusion (include_path=’.:/usr/share/php:/usr/share/pear’) in
/var/www/wp-content/plugins/wp-super-cache/wp-cache.php on line 65
Warning:
include_once(/var/www/xx/xx/xx/xx/xx/xx/wp-content/plugins/wp-super-cache/ossdl-cdn.php):
failed to open stream: No such file or directory in
/var/www/wp-content/plugins/wp-super-cache/wp-cache.php on line 82
Warning: include_once(): Failed opening
‘/var/www/xx/xx/xx/xx/xx/xx/wp-content/plugins/wp-super-cache/ossdl-cdn.php’
for inclusion (include_path=’.:/usr/share/php:/usr/share/pear’) in
/var/www/wp-content/plugins/wp-super-cache/wp-cache.php on line 82
Looking in the file wp-cache.php on lines 65 and 82, it says that :
include(WPCACHEHOME . 'wp-cache-base.php');
Path ‘dirname(FILE).’/…wp-cache-base.php’ not found Include
expression is not resolved
include_once( WPCACHEHOME . 'ossdl-cdn.php' );
Path ‘dirname(FILE).’/…ossdl-cdn.php’ not found Include expression
is not resolved
So I was thinking about changing the path. However, this is bothering me because I am afraid that this action will be potentially a troubleshooting cause when the plugin will have to be updated.
I have no ideas how I can fix it.
Uninstall and reinstall the plugin ?
Use an other plugin to manage the cache?
Thank you in advance for your answers. Have a nice day!
WP Super Cache puts the below line in your wp-config.php file. Remove the line from your wp-config.php file and reinstall and reactivate the plugin.
define( ‘WPCACHEHOME’, ‘/home/USERNAME/public_html/wp/wp-content/plugins/wp-super-cache/’ ); //Added by WP-Cache Manager
I encountered the same problem after moving my Wordpress directory to the root of my site. If you get the problem and can't deactivate the erroring plugin, go to your /wp-content/plugins/wp-super-cache and remove or rename the directory. This will manually deactivate this so you can install a fresh instance.
A friend of mine asked me to move wordpress website from development server to production. I've copied all the files, backed up and restored database. After that I'd changed sitename and home values in database (_options table) to new domain and it started. Though only home page is working fine. When I navigate to any other page it gives me 500 error. In error_log I got following errors:
1423021301: /home1/crankst1/public_html/fish-dev-site/ssv3_payload_extractor-r0Xkqq2xFD.php startup
[24-Feb-2015 19:16:59 UTC] PHP Warning: require_once(/home1/crankst1/public_html/fish-dev-site/wp-content/plugins/js_composer_theme/include/classes/core/class-vc-sort.php): failed to open stream: No such file or directory in /home1/crankst1/public_html/fish-dev-site/wp-content/plugins/js_composer_theme/js_composer.php on line 168
[24-Feb-2015 19:16:59 UTC] PHP Fatal error: require_once(): Failed opening required '/home1/crankst1/public_html/fish-dev-site/wp-content/plugins/js_composer_theme/include/classes/core/class-vc-sort.php' (include_path='.:/usr/php/54/usr/lib64:/usr/php/54/usr/share/pear') in /home1/crankst1/public_html/fish-dev-site/wp-content/plugins/js_composer_theme/js_composer.php on line 168
Paths that cause errors are related to development server and I can't find where to change them. I'm not very good with wordpress, so I suppose that solution should be very simple.
I'm sure there is an issue with a plugin http://codecanyon.net/item/visual-composer-page-builder-for-wordpress/242431/comments?page=149 try to see if there are any hardcoded paths on the plugin dashboard.
Delete your .htaccess file then go to the permalinks page change to another permalink type save page then change back to permalink you had this will force wordpress to recreate the .htaccess file and it will allow all pages you have to show correctly on the site. :-)
I have problem with my server configuration. I use Apache 2.216, PHP 5.3.3 and wordpress 3.4.2 with Shopperpress. Time to time I receive error "client denied by server configuration: path/to/file" in apache log file. It is path to _tbs.php file, but it is not problem in rights of file, because this file is called 12 times on page for getting thumbs of photos and there is error only several times. I think that it has no connection to concrete photo, because once this photo is displayed corectly and next time same photo produce error.
Do you have any idea what can be reason?
Thank you for all advices.
Viktor
I think thats a problem by the configuration of MaxClients or MaxRequestsPerChild.
Try to restore the default configuration and try it again. If that not works, reinstall Apache and purge the old configuration.
You have given very little information. It is not clear under what conditions do you work (OS, installed modules, Log entrys,...).
WordPress 3.4.2 is very old and safety-relevant. Please update WordPress and your WP-Plugins.
Go to you VHOST-file and replace:
Deny from all
Allow from 127.0.0.0/255.0.0.0
with:
Require all granted
This cause for old Config-Files and newer Apache-Version. Since Apache 2.4.3 a new security feature is added.
I've got very simple .WAR containing example servlet. I'm able to deploy it in servicemix using the following command:
osgi:install file:///home/seiho/apache-servicemix-4.4.2/deploy/TestServlet.war?Bundle-SymbolicName=TestServlet&Webapp-Context=/TestServlet
And then see it in my browser. But only with full path to a file, e.g.: localhost:8080/TestServlet/index.html or localhost:8080/TestServlet/TestServlet (my servlet is TestServlet class).
I'd like to launch the index.html page automatically after entering: localhost:8080/TestServlet
how to do it?
MORE IMPORTANT
I need a way to convert the .WAR file or servlet project (I've got the sources) so that new .WAR file can be auto-deployed by copying it to $SERVICEMIX_HOME/deploy directory.
I've tried editing the MANIFEST.MF file, but with no success. Probably I'm doing something wrong.
Thanks for any advice/help.
To be recognised as a wab, you need to add a context path header to your manifest:
Web-ContextPath: TestServlet
It's working now! I was doing my MANIFEST.MF according to this page: http://team.ops4j.org/wiki/display/ops4j/Pax+Web+Extender+-+War+-+OSGi-fy
The problem was that for some reason "Bundle-Version: 1.0" line was required as opposed to optional as stated on that page.
Honestly, just adding the Bundle-Version fix-it.
I knew it was something wrong with the MANIFEST.MF and after Holly Cummins' question I played with it a bit more. Thanks Holly.
I still can't do anything with the manual site launching (have to manually enter the index.html).
http://localhost:8080/TestServlet/ gives me this:
HTTP ERROR 404
Problem accessing /TestServlet/. Reason:
Not Found
Powered by Jetty://
http://localhost:8080/TestServlet/index.html gives me proper site.