Nice so we can just extend on this assetsRules for the fields and back-ends. So it works just like the old paramsBuilder now extensionsParams. I think this will work great!

Nice so we can just extend on this **assetsRules** for the fields and back-ends. So it works just like the old **paramsBuilder** now **extensionsParams**. I think this will work great!

Llewellyn reviewed 2017-08-22 22:57:17 +00:00

admin/views/joomla_components/view.html.php

Llewellyn commented

2017-08-22 22:57:17 +00:00

Author

Owner

Well if you removed all components then you could not import any... so I moved the button to function only that does not requirer a selection, so it will show even if there is no items. I can see it messed up the lineup... 👎 will see if we can fix that. But it has to show even if there is no items.

Well if you removed all components then you could not import any... so I moved the button to function only that does not requirer a selection, so it will show even if there is no items. I can see it messed up the lineup... :-1: will see if we can fix that. But it has to show even if there is no items.

Llewellyn reviewed 2017-08-22 22:57:33 +00:00

admin/helpers/compiler/e_Interpretation.php

Llewellyn commented

2017-08-22 22:57:33 +00:00

Author

Owner

Yea it is a start!

Llewellyn commented

2017-08-23 14:55:14 +00:00

Author

Owner

@mwweb is this working for you? can I bump the version upgrade?

ro-ot (Migrated from github.com) approved these changes 2017-08-23 15:14:21 +00:00

mwweb commented

2017-08-23 19:44:40 +00:00

(Migrated from github.com)

Author

Owner

This worked fine on the demo component.

I think this is a good start on it. At least the site views can be automatically set to public. Perhaps sometime in the future we can look at, and discuss, extending this even further. An example, create and edit permissions you generally wouldn't want public, but at least registered. But that can be a start.

This worked fine on the demo component. I think this is a good start on it. At least the site views can be automatically set to public. Perhaps sometime in the future we can look at, and discuss, extending this even further. An example, create and edit permissions you generally wouldn't want public, but at least registered. But that can be a start.