简体   繁体   English

Apigility Admin UI无法打开

[英]Apigility Admin UI Not Opening

so my apigility admin area was working just fine before they updated it to ZF3. 所以我的权限管理区域在将其更新为ZF3之前工作正常。

No after composer update, I am getting this when I try to open /apigility/ui 作曲家更新后没有,尝试打开/ apigility / ui时得到此提示

/ apigility / ui页面

Does anyone know what might be the problem and how can we resolve this issue ? 有谁知道可能是什么问题,我们如何解决这个问题?

The Issue is: In the error logs you'll find that css and js data is not loaded. 问题是:在错误日志中,您会发现未加载CSS和JS数据。 As the rwoverdijk/assetmanager is removed since apigility Admin 1.5 some files are not loaded anymore. 由于自apigility Admin 1.5起删除了rwoverdijk / assetmanager,因此不再加载某些文件。

Solution: Follow part 2. of the Upgrade from https://github.com/zfcampus/zf-apigility-admin#initial-upgrade-to-15 解决方案:https://github.com/zfcampus/zf-apigility-admin#initial-upgrade-to-15遵循升级的第2部分。

I also tried part 1 what was also working because now the rwoverdijk/assetmanager is now on 1.7.1 (but i do not know if the incompatibility is solved with this version so i did it with the zfcampus/zf-asset-manager). 我还尝试了第1部分,由于rwoverdijk / assetmanager现在处于1.7.1上,所以它也起作用了(但是我不知道该版本是否解决了不兼容问题,所以我用zfcampus / zf-asset-manager做到了)。 I'm still on ZF2 but the issue is the same. 我仍在使用ZF2,但问题是相同的。

Install zf-asset-manager. 安装zf-asset-manager。 This is a Composer plugin, and operates when installing or uninstalling a package. 这是一个Composer插件,可以在安装或卸载软件包时使用。 If you add this, you will need to follow these steps: 如果添加此,您将需要按照以下步骤操作:

composer require --dev zfcampus/zf-asset-manager

rm -Rf ./vendor

composer install

The additional steps are necessary in order for the plugin to pick up on the assets from the other components and copy them to the public folder. 为了使插件能够从其他组件中提取资产并将它们复制到公用文件夹,必须执行其他步骤。 After installation you ll find a folder apigility-ui in you 安装后,您会在其中找到一个文件夹apigility-ui

Something similar happened to me when I reused the same code for a new repository on my local development environment having set the base_path value on ./module/Application/config/module.config.php . 同样的事情也发生在我身上时,我在我的本地开发环境已经设置./module/Application/config/module.config.php的BASE_PATH值重新用于新的存储库相同的代码。

'view_manager' => [ 'base_path' => ' https://subdomain1.example.com ',..] 'view_manager'=> ['base_path'=>' https: //subdomain1.example.com',..]

I solved it by deleting the base_path config value. 我通过删除base_path配置值解决了它。

The view cannot be rendered fully as the wrong html base is injected to the rendered view. 该视图无法完全呈现,因为将错误的html base注入了呈现的视图。 In my case the html base looked like 在我的情况下,HTML base看起来像

<base href="http://subdomain2.example.com.devhttps://subdomain1.example.com/">

Instead of 代替

<base href="http://subdomain2.example.com.dev">

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM