子域不读取站点/所有/下的模块或主题文件夹
我用 drupal 设置了一个网站，一切都很顺利。然后我添加了一个子域，这也很好，直到我启用站点/所有/主题文件夹下的自定义主题。该主题在管理面板中无法正确显示（没有缩略图），并且激活后，该网站似乎根本没有结构。
我尝试使用的主题在我的其他网站上完美运行，因此主题本身不是问题。我注意到 all/ 文件夹下的模块也发生了同样的情况。但是，它可以使用根主题和模块文件夹下的任何内容。
所以有些东西阻止它正确加载/读取站点/所有/文件夹。将所有内容转储到 core 文件夹当然并不理想，但我无法找出问题所在。
编辑：解决了！ 不知何故，htaccess 文件进入了站点文件夹，其中包含重定向。仅导致子域无法正确看到子文件夹，只有根目录。
I have a site set up with drupal, everything going fine. I then added a subdomain, and that too was fine until I went to enable a custom theme that was under the sites/all/themes folder. The theme does not show properly in the admin panel (no thumbnail), and when activated, the site appears to have no structure at all.
The theme I am trying to use works flawlessly on my other sites, so the theme itself is not a problem. I noticed the same happens with modules under that all/ folder. It is able to use anything under the root themes and modules folder however.
So something is preventing it from properly loading/reading the sites/all/ folder. Dumping everything into the core folder is not ideal of course, but I can't figure out the problem.
Edit: RESOLVED!
Somehow an htaccess file got into the sites folder with a redirect in it. Causing just the subdomain to not see the subfolders properly, only root.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果
sites/all下的主题和模块对于两个站点（主站点和您的子域）均不可用，则问题可能与文件夹的可访问性有关。无论您使用哪个用户帐户访问网站，几乎可以肯定网站服务器本身（无论是 Apache、IIS 还是 Xyz）都以不同的帐户运行。如果该帐户无权扫描和读取
sites/all下的文件，那么它们将不会显示。比较常规
modules目录和sites/all之间的权限（以及用户/组详细信息，如果在 Unix 服务器上运行）以查找任何差异，并修复发现的任何差异。If the themes and modules under
sites/allare unavailable for both sites - the main site and your subdomain - then the problem may be around accessibility of the folder.Regardless of the user account you use to access the site, it's almost certain that the website server itself (whether Apache, IIS or Xyz) runs as a different account. If that account doesn't have rights to scan for, and read, files under
sites/allthen they won't show up.Compare the permissions (and user/group details, if running on a Unix server) between your regular
modulesdirectory andsites/allto find any differences, and fix any you find.