I uploaded an extension to the project from the shopware admin panel. The extension is active and I can set the configurations. The problem is the module doesn't show up under Settings > Extensions. How can I fix this problem?
It would be helpful to know which module you are talking about.
Anyways, each module you install should appear under Extensions -> My Extensions and you can configure basic settings (those which are added by the developer via config.xml) in the extension list, ...-menu and then "configuration". I assume think that is already working in your case.
If the module you installed did not add extended configuration capabilities, then it will not be visible under Settings -> Extensions - so this is completely normal and not an error.
If you are developing that module and need extended settings, you have to add them via a VueJS / javascript module. This works roughly the same as adding pages anywhere else in the admin panel.
Like Alex said, the configuration options do not appear by default under Settings -> Extensions for any given plugin.
If you want to add something like this to your plugin, you're going to have to specify a settings item in your JS module, looking like this
settingsItem: [{
group: 'plugin',
to: 'my.custom.route',
icon: 'my-plugin-icon',
name: 'my.custom.settings.title'
}]
Of course, you are going to need a page for my.custom.route.
A working example of both can be seen in the module registration file and page registration file of the FroshPlatformAdminer plugin
Related
Noticed that Azure DevOps is no longer showing the menu options in Project Settings for the Extensions.
Does anyone else see this or know why?
I am unable to update settings for the installed extensions.
You can manage the installed extensions in the Organization settings.
Go organization settings--> Extensions under General. See document here for more information.
I have seen the same thing, and it only occurred recently. Yes, the org level extension management is still there, and that only allows for managing which extensions are available to use.
The configuration for the extension usage within each project was a separate section in the project settings - this is missing entirely. We have need to modify one of our extension configs and can no longer access it to do so.
I believe this must be an Error of type PEBKAC coming from a recent MS update to DevOps.
I am working on setting up a Hybris B2B instance and when I look in HAC's Extensions the storefront has a red X, not a green checkmark. I assume that means there is an error somewhere, where do I go to find the error?
Some background on what I have done:
extract Hybris 1811
install -r b2b_acc_plus
ant clean all
ant modulegen and selected accelerator...
ant clean all
ant initialize
hybrisserver.sh
At that point the server is running, I can get to the HAC, but cannot get to the storefront. I am guessing I might be missing a step, too, but all the same, there are other extensions that have the red X so I would like to understand how to explore the reason why.
Red Cross against storefront extension in Hybris Admon Console is to depict that its not a backoffice/hmc extension.
You would also notice a green check to depict its a core module.
Also in front of storefront extension, you willl not the webroot URL. Normally its default value is /yacceleratorstorefront unless one changed it.
You should be able to access storefront using
http://localhost:9001/yacceleratorstorefront?site=apparel-uk
You can change site param in URL to access any of the configured websites.
Example
...?site=electronics
...?site=apparel-de
Alternatively, you can add URL mapping in host file.
Make the following entry in your hosts file:
127.0.0.1 apparel-uk.local apparel-de.local electronics.local
Once your hybris server is running, you can access any of the following URLs:
http://electronics.local:9001/yacceleratorstorefront/
http://apparel-uk.local:9001/yacceleratorstorefront/
http://apparel-de.local:9001/yacceleratorstorefront/
Thanks
I'm using a company-hosted GitLab Community Edition 11.0.2.
There used to be a menu entry 'Issues' under each project.
For some projects there still is, but not for a specific one.
I remember in previous versions it was possible to turn that feature on/off via the project-settings, but I simply can't find that setting anymore.
It should be included in the Core/Free version, though (Issue Boards has a checkmark for all versions, including Core here: https://about.gitlab.com/pricing/self-managed/feature-comparison/)
How can I enable the built-in issue feature for my personal project?
(I don't need anything fancy, just a list with issues and statuses)
It sounds like it has been disabled for the project (or the company admin has just disabled Issue boards by default on the instance).
You can re-enable it if you are a Maintainer/Owner/Admin for the project in:
Project -> Settings -> General -> Permissions
Project settings documentation.
For some reason I cannot get this to work. I'm following the exact procedure described here
http://developer.chrome.com/extensions/external_extensions.html#registry
And I still cannot get the extension listed. If I install it manually, using "Add Unpacked Extension" it works just fine.
Any help would be greatly appreciated
One of many writeups on this subject:
Google on Friday announced that it is changing its stance for silently
installing extensions in its browser. As of Chrome 25, external
extension deployment options on Windows will be disabled by default
and all extensions previously installed using them will be
automatically disabled.
You're much better off submitting your extension to the Chrome Web Store. If you really want to install off-store, consider inline installation.
I have been struggling with installing an addon via the registry as well. I was successful with installing an addon without adding reg keys. And using the preferences file.
I extracted my extension to Local\Google\Chrome\User Data\Default\Extensions\${ADDONID}\${VERSION}
I then added my extension directly to the Preferences file in Local\Google\Chrome\User Data\Default under the section extensions settings ${ADDONID} <-- add your extension. Compare the Preferences file to an instance you have already installed your addon. And copy that to the Preferences file along with the extension directory on a fresh install. And it should work.
This thread gave me some direction:
https://superuser.com/questions/462804/how-to-copy-an-extension-from-one-chrome-installation-to-another
Hi StackOverflow team !
I've created an Eclipse RCP desktop application which has an extra menu called 'Help' in the menubar. I didn't create it from any of usual ways like adding actionSets extention, or creating and registering the actions from ActionBarAdvisor.java of the project. I don't need it anymore. Please, suggest me how can i remove it from my Menubar ?
It's sounds like the help UI plug-ins are being included within your run configuration
Couple of things to check...
-- Have a look at your application's .product file, and see which plug-ins are defined, and see if the org.eclipse.help.ui plug-in is defined (org.eclipse.help is probably defined since org.eclipse.ui.workbench requires it, but this won't cause the menu to appear)
-- If you are running within Eclipse, open Run --> Run Configurations, select the Eclipse application you are running and check the plug-ins tab. If it is launching with 'all workspace and enabled target plug-ins' then this will be picking up the help UI plug-ins too. Even if it's not set to this option, check the plug-ins ticked to see if the org.eclipse.help.ui is defined.
This configuration should only use the plug-ins required for your application. If it was created by using the 'Launch an Eclipse Application' option from within the .product file, the configuration created should match the plug-ins defined in that.
It's also worth making sure that no other plug-ins use org.eclipse.help.ui - this can be easily seen by removing it, and then pressing the 'Validate Plug-ins' button within the run configuration dialog, it will show you if anything has been broken after removing it