WebsiteBaker Support (2.12.x) > Modules

Hints Version: 0.6.0

<< < (3/3)

Martin Hecht:
Hi Henri,

I agree with jacobi22. Probably you have changed the menu setting by accident when you have added the permission for the new group to the page.

About the popup: Each Hints section is specific to its page, more precisely to the "modify page" area of that page. The hints are not global to the whole backend. Or did you add Hints sections on the other pages, too (visible to the new group!) and they still do not appear?

Best regards, Martin

henri:
Hi jacobi22 and Martin,

Now Hints works fine in the hidden page.
And now it is clear that Hints only works for that page where the Hints module has been added.

Concerns the Menu setting had changed from Footer menu to Main menu. For me a big riddle because there were 6 menu items in Footer that were moved to the menu at the top of the page. And at Modify Page I was only right at administrators with the mouse.

It would be great if Hints in admin of website baker would be at the top of the menu.

see screenshot

Martin Hecht:
Hi Henri,

The possibility to have add or view hints right from the main menu of the backend would require a substantial modification of the WebsiteBaker core. Addons are supported for cintent  of sections, for adding support of a specific language, for backend and frontend templates (only the layout, but not new functionality), admin tools in the Tools area (Beheerfunctues I believe in Dutch), and the Snippets which provide functions that can be called by other addons.

Sure, several ideas in the Hints module would be nice to have in general, e.g. the fine grained access rights on a "per section basis", but the core package can not pick up each and every idea that appears to be useful in some usage scenario. One of the advantages of WB is that it is not too complex and quite easy to use even for beginners with close to zero background knowledge about content management systems.

We have discussed several aspects before I have decided to write the Hints module. The implementation as a content addon that is only visible in the backend, with a built-in permission management was the most straight forward path to go. Maybe, if future WB versions are more flexible, e.g. when there is an interface to register user-defined functions to the menu bar, or when it is possible to inject user-defined content at each place of the backend, things look different, but for now the only solution would be a fork of the backend theme (to insert a new item in the menu) in combination with an own infrastructure to hold the information which hint shall be shown where (there are no page ids or section ids for the whole backend. They onty exist in the page tree).

Best regards
Martin

Navigation

[0] Message Index

[*] Previous page