Stores Configuration tabs display is broken ?
Closed this issue · 8 comments
Hi,
After installing, I got Stores > Configuration tabs broken :
- Does not display left tabs column
- Only display last left column item content
cf screenshot
Got others installed extensions but occured only after Doofinder install.
Installation was tested by FTP drop and composer.
Tried to find something wrong in system.xml but all seems to be OK.
Am I doing something wrong ?
Thank you
Magento V2.2.4
Hi @aurelienInternetrama . What's the version of the module you're using? How did you installed it? Did you clean cache?
You could try to execute this in the CLI:
$ php bin/magento setup:upgrade
$ php bin/magento setup:di:compile
$ php bin/magento cache:flush
Hi @carlosescri and thank you for reply.
Version I'm using is 0.1.4-beta
Three tests were done for installation :
- composer like
- Magento marketplace like
- Direct FTP drop then command lines
Cache was cleaned (several times)
And command lines were already executed.
Hello @aurelienInternetrama
Could you provide content of etc/module.xml file?
Hi @magently ,
Here it is :
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:Module/etc/module.xsd"> <module name="Doofinder_Feed" setup_version="0.1.4" /> </config>
Thanks
@aurelienInternetrama
Anything in logs? Is this your first installation of the module?
Hi @magently,
Nothing in logs anywhere server or Magento.
Yes it's the first time I install this module for Magento 2 (already installed Magento 1 extension, really great work :) ).
Thought missing tabs were just hidden due to bad CSS or something about display but they're just not there in HTML.
Tab id "doofinder_config" is not a reserved one, not overriding or rewriting anything, I don't really understand the issue. XML files format seem OK. Magento command line told Doofinder_Feed well installed.
Is it possible there's an issue about Model files used in Stores > Config tab forms that would create break but I think that if it was a PHP issue, we got logs somewhere.
Really disappointed
Thanks
We had the same problem but it was occurred by <sequence>
tag in module.xml. We have already fixed it. We are not able to reproduce it. But we will keep looking at it.
@magently,
OK thanks