admin管理员组文章数量:1125742
Here is the scenario:
I would like to design a brand new wordpress admin for my clients (using WordPress autoload
as the core to interact with WordPress). I have tried slightly modifying the css or even using javascript to manipulate DOMs, but it just seems very inefficent while I can just re-code a new page instead of manipulating existing page.
With that in mind, I created a new folder, say, custom_dashboard
, and try to redirect the clients there whenever they visit /wp-admin
. However, it always shows 404 NOT FOUND
when I open mydomain/custom_dashboard/index.php
or anything that is not /wp-admin
.
My questions are:
- What are some recommended approaches this problem? Is manipulating CSS & javascript via
wp_enqueue_script
andwp_enqueue_style
the only possible way to recreate the new dashboard? - How do I allow direct access to a single folder/file within the WordPress installation?
Here is the scenario:
I would like to design a brand new wordpress admin for my clients (using WordPress autoload
as the core to interact with WordPress). I have tried slightly modifying the css or even using javascript to manipulate DOMs, but it just seems very inefficent while I can just re-code a new page instead of manipulating existing page.
With that in mind, I created a new folder, say, custom_dashboard
, and try to redirect the clients there whenever they visit /wp-admin
. However, it always shows 404 NOT FOUND
when I open mydomain.com/custom_dashboard/index.php
or anything that is not /wp-admin
.
My questions are:
- What are some recommended approaches this problem? Is manipulating CSS & javascript via
wp_enqueue_script
andwp_enqueue_style
the only possible way to recreate the new dashboard? - How do I allow direct access to a single folder/file within the WordPress installation?
1 Answer
Reset to default 1Since you asked for recommended approaches...
Why code your own custom dashboard? What is WordPress not doing that yours would?
WordPress is 15 years old with contributions from hundreds of developers. Are you sure that your dashboard is going to be better, and worth your time (or your clients' time) to code?
I don't mean that to be rude at all. Maybe you have a valid reason that you need a custom dashboard. But it would take a lot to convince me it's a better route than just extending or modifying the WordPress one. And the first part of that convincing would be telling me what you hope to gain. What is unique about your situation?
In answer to your second question, that doesn't sound like a WordPress issue, but rather a server or file issue. Here's why:
The way WordPress works on the server is that everything is rerouted to index.php. This bootstraps the WordPress process, including the handling of rewrite rules for all other paths. The way that the requests are rerouted to WordPress is important here:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
This is the standard Apache .htaccess WordPress redirect block. In English, line by line, it would read:
- If the server can handle redirects:
- Get ready to redirect
- We'll be talking about the / directory
- If the request is for index.php, great! Do nothing, we're done.
- If the request is NOT for a real, existing file...
- and if the request is NOT for a real, existing directory...
- ...then redirect to index.php
- End of code that only runs if the server can handle redirects
So the important part for your case is that, in a nutshell, requests only get redirected to WordPress if they aren't actually real files or directories. Since you said they are real files and directories, something seems to be misconfigured on your server.
Please make sure that the files are present, that their permissions are correct (For instance: directories set to 755, files set to 644), and that the path you are attempting to access them at is correct. For real files at mydomain.com/custom_dashboard/index.php, that folder would be in the same directory as wp-content and wp-admin, but not inside either of them.
本文标签: pluginsAllow direct access to filesfolders within Wordpress to replace wpadmin
版权声明:本文标题:plugins - Allow direct access to filesfolders within Wordpress to replace wp-admin 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1736604933a1945302.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论