Back to Backend Skin Support

Troiscent
Troiscent

Hello,

I create some plugins using the excellent builder plugin, but I don't like the look of default models forms. I prefer to transform secondary table to a right sidebar, and use the "fancy-layout" style to have an orange header to handle the "title" and "slug" fields (like the rainlab blog plugin + a right sidebar).

I wonder if that plugin would allow me to define a default create.htm and update.htm file that would apply to all my plugins. If yes, could you explain me how ?

Thanks

cydrick.nonog
cydrick.nonog

Hi @Troiscent,

You can do this also without using backend skin. You can copy the controller view in rainlab blog and copy it to your plugin.

You can also do this using the backend skin. In backend skin, you can change each specific plugin.

I recommend you using Backend Skin if you desire to change the whole look of octobercms backend.

Thanks.

Troiscent
Troiscent

Hello,

Thank you for the answer.

The this is that I want to transform secondary tabs that I found useless to a right sidebar. Like the one you can find on backend/backend/users/myaccount url.

I create a lot of plugins thanks to the builder plugin and I don't want to always override the create.htm and update.htm file with a modified version converting secondary tabs into a sidebar.

That's why I wonder if this plugin would allow me to globally define it, and get the correct layout with sidebar automatically when I create a new plugin.

Thanks

Alex

Dreqnoid
Dreqnoid

First of all, this is an awesome plugin!

Is it also possible to change the _search.htm from \modules\backend\widgets\search_search.htm?

I've tried: {theme}/backend/views/modules/backend/widgets/search/_search.htm but without results.

cydrick.nonog
cydrick.nonog

Dreqnoid said:

First of all, this is an awesome plugin!

Is it also possible to change the _search.htm from \modules\backend\widgets\search_search.htm?

I've tried: {theme}/backend/views/modules/backend/widgets/search/_search.htm but without results.

Sorry for late reply, for the fix of this bug. You need to update the plugin to 1.0.4

1-5 of 5