e from them in such case. Once below comments are fixed
> I
> think we can move it under theforeman org (unless someone objects).
>
>
> On Friday 13 of May 2016 03:59:18 oprazak wrote:
> > Thanks for comments, I made some changes and took care of the following:
> >
>
There was an issue with webpack when running in a vagrant box and serving
assets over https. Have a look at:
https://github.com/theforeman/foreman/commit/ab5c7c28f3c8e6a4fd4731cba590b62d5497ac97
':webpack_dev_server_https: true' in settings.yml fixed the console errors
for me
On Friday, August
Hi everyone,
if you are a plugin developer/maintainer and your plugin has host_extension
that adds inheritable attributes to host, then read on. In a recently
merged bugfix [1], there has been a change that possibly breaks your plugin.
I have already submitted PRs to katello [2] and foreman_opens
I believe there is already a related feature request in our Redmine:
http://projects.theforeman.org/issues/10799
On Wednesday, September 14, 2016 at 4:13:43 PM UTC+2, Thomas Fee wrote:
>
> I'd want the user to be able to edit, generally, but just want to be able
> to set a "readonly" flag on som
Hi,
I never tried to add items into plugin's menu from another plugin, but I
think the issue here is that plugin registration is not ordered in any way.
So if you have plugin A with
sub_menu :top_menu, :ConfigMonitor
#...
end
and plugin B with:
menu :top_menu, :patchmanagement, :parent => :Con
Hi,
I recently started identifying problematic areas in Permissions and Roles,
especially with regard to plugins. Foreman provides 'Viewer' and 'Manager'
roles out of the box and users expect these roles to work for plugins as
well. But plugins generally do not add their permissions to core's ro
