Directory Forbidden Neat Bourbon in Wordpress Editor - wordpress

We are creating a theme on Wordpress that makes use of Neat Bourbon. On the frontend everything works great. On the backend we are trying to display the content the way it will look so we also call Neat Bourbon. Our issue is Neat bourbon throws an error in nginx that the directory is forbidden. This is the only directory showing this error.
[error] 11438#0: *290 directory index of "/var/www/wp-content/mu-
plugins/folder/bower_components/neat/core/neat/" is forbidden, client:
XX.XX.XX.XXX, server: www.example.com, request: "GET /wp-content/mu-
plugins/folder/bower_components/neat/core/neat/ HTTP/2.0", host:
"www.example.com", referrer:
"https://www.example.com/wp-admin/post.php?
post=1318&action=edit"
Permissions are all the same:
List of folders and their permissions
Any help would be greatly appreciated.

Seems like your GET url is incorrect. The last neat is a sass file and not a directory.
Depending on how you are running your imports, the path should be one of the following.
/wp-content/mu-
plugins/folder/bower_components/neat/core/neat
/wp-content/mu-
plugins/folder/bower_components/neat/core/_neat.scss
See: https://github.com/thoughtbot/neat/blob/master/package.json#L28

Related

Using uninitialized "redirecttoindex" variable

Suddenly out of nowhere I can not log in into my WordPress site. The site is working but wp-admin is not. In the error log I get:
2022/07/04 23:45:58 [warn] 31793#31793: *300658 using uninitialized "redirecttoindex" variable, client: ip.000.000.000, server: mydomain.com, request: "GET /wp-admin/HTTP/2.0", host: "mydomain.com"
How can I debug this? I have just got this site for maintenance and I am not very familiar with WordPress. Should I diff it with the original version and see if files are modified?
I scanned the code and there are no redirecttoindex variables. Is something up with nginx?
I also can not find anything on google with such a query.
Server API: FPM/FastCGI
PHP Version 7.4.26
nginx/1.20.2
You confirm the other pages in the sites this working well ? If the answer is Yes, you need the check if exists some plugin what redirect the route of wp-admin for new route. First we have to activate the debug mode in the wordpress in the file wp_config find de const WP_DEBUG and set true.
P.S: DonĀ“t activate the DEBUG in the product view.

CSS code not being applied to my flask application

I am learning how to build flask applications. But, whenever I write some CSS code, and link that to my html template, the css never gets applied. No matter what I do.
Here is the line that links my html template to my css file:
<link rel="stylesheet" href="{{ url_for('static',filename='css/base.css') }}">
Here is what I did:
I tried restarting my server.
I searched for this online. This is what I found: CSS not being applied in Flask app. However, even that did not help.
I believe my server does not find my css file, because this is the entire output in my terminal:
* Serving Flask app "app" (lazy loading)
* Environment: production
WARNING: This is a development server. Do not use it in a production deployment.
Use a production WSGI server instead.
* Debug mode: on
* Restarting with stat
* Debugger is active!
* Debugger PIN: 222-949-106
* Running on http://127.0.0.1:5000/ (Press CTRL+C to quit)
127.0.0.1 - - [11/Nov/2020 21:18:46] "GET /login HTTP/1.1" 200 -
127.0.0.1 - - [11/Nov/2020 21:18:47] "GET /login HTTP/1.1" 200 -
As you can see, my css file is not mentioned anywhere. Where is the mistake?
Please help me.
I hope this is because of the cache. The browser will load CSS once from the server and then it will be stored in the cache memory.
You do remove the cache memory by Shift + F5.
Note: If you may think that the server does not find your CSS file, but if it can't able to find the file, you may encounter with 404 error. In your case, you didn't get that error. So the only possible answer is CACHE.

Unable to render CSS in MAMP localhost

I am experiencing something very strange when implementing the Metronic Admin panel into a new Laravel project. I have broken everything up into partial blade files, and included all CSS and JS using the standard
{{ asset('...') }}
blade syntax. The problem I am facing is the loading of a single CSS file, in that all browsers will hit this point and stop. What is even weirder is that there are no console errors and no output in the performance tab in Chrome, everything just hangs.
The CSS file in question is
<link href="{{ asset('admin/demo/demo3/base/style.bundle.css') }}" rel="stylesheet" type="text/css" />
Unminified, this CSS file is 55,000 lines long so I'm not too sure if this is something to do with just the sheer size of the file, however, leaving Chrome for 15 minutes has not produced any results at all.
I am able to open the static HTML file from the download folder, which links to this same file and renders perfectly fine, using the file:// method, but when these files are added into the localhost path, the same problem happens again. This leads me to believe this is not a problem with Laravel, but a problem with the localhost instance instead.
The localhost is running the latest version of MAMP on Windows 10, not had any other problems with any other sites, just this single CSS file.
I can also see in the Apache access.log file that these assets are being found with a 200 status code
127.0.0.1 - - [29/May/2018:21:05:41 +0100] "GET /digitaltools/public/home HTTP/1.1" 200 623
127.0.0.1 - - [29/May/2018:21:05:41 +0100] "GET /digitaltools/public/admin/vendors/base/vendors.bundle.css HTTP/1.1" 200 357894
127.0.0.1 - - [29/May/2018:21:05:41 +0100] "GET /digitaltools/public/admin/demo/demo3/base/style.bundle.css HTTP/1.1" 200 1736133
Any help would be greatly appreciated.
After a clean install of MAMP this seems to have solved the problem. Very strange behaviour.

Server respond with a status 403 (forbidden)

I'm using asp.net MVC. I have hosted my website on appharbor. Everything is working fine on localhost. On live website I'm getting error.
Server responded with a status of 403 (Forbidden)
To solve this issue. I added <modules runAllManagedModulesForAllRequests="true" /> in web.config but it didn't work.
Another solution is I need to You need to change permissions on the folder bootstrap/css. To change permission I have to type command sudo chmod 0777. But I cannot figure out where to type this command.
So where I have to type this command or what is the alternative to tackle this 403 issue.
I know this is a little old, but I had the same problem now with jstree.
I don't know if you realized, but this behavior is given to you by the EnableOptimizations.
Basead on Denis Ivin answer here, you probably have a jstree folder inside Content/plugins and IIS, instead of giving you the jstree.css, is trying to list the folder and that is, by default, forbidden.
In my case I had to do the following for the plugin work as intended:
BundleConfig.cs
bundles.Add(new StyleBundle(
"~/Content/plugins/jstree/jstree")
.Include("~/Content/plugins/jstree/style.css"));
View.cshtml
#section css{
#Styles.Render("~/Content/plugins/jstree/jstree")
}

Magento CSS/JS not loading after upgrade to 1.8.1

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 :)

Resources