News and Announcements

  • entries
    500
  • comments
    13,835
  • views
    4,816,506

Contributors to this blog

IP.Board 3.2.0 Dev Update: Applications Improvements

Parts of this entry may only apply to those who create applications for IP.Board. Feel free to skip the sections that may not interest you.

In my last blog entry I mentioned the improvements we have made for the hooks system, in this new entry I'll talk about the changes we have made for applications.


Disabling an Application

When an application is disabled from the ACP a check is performed on all the enabled hooks that have it listed in their requirements and a warning will appear at the top of the page to warn the admin about disabling them.

blogentry-126321-0-53719800-1299081160_t


Application Tab Permissions

We have received several requests from our customers in both the feedback forum and tickets and we decided to include it in IP.Board 3.2, you will now be able to specify for which groups the application tab will appear on the public side! The setting to control this is an easy multi-dropdown menu, furthermore we have renamed the setting "Hide Tab" to "Hide for all current and future groups?" and we have moved it under a new permissions tab.

blogentry-126321-0-03935100-1299081183_t


Global Caches

As we have already mentioned for the hooks (see previous blog entry) we have added support for the "Global Caches" system in the applications too, this will allow modification developers to also specify for applications which additional caches should be loaded on each page together with the default ones. For example we will use this in our IP.Nexus application and specify the "nexus_ads" cache which is currently loaded separately on each page when the application is enabled.

blogentry-126321-0-53384800-1299081173_t


Updates Checker

Unlike hooks the applications had no way to check for updates, we have now added 2 new settings "Website" and "Update URL" which are used in the same exact way as the one for the hooks (see the previous blog entry).
The updates available will show as a purple badge similar to the ones for the hooks and a counter of the updates available will show up at the top of the page as well.

blogentry-126321-0-87054700-1299081176_t blogentry-126321-0-01722100-1299086351_t


Sphinx Cronjobs

When Sphinx is enabled we often have customers confused on how to setup properly the cronjobs based on the applications installed. To solve this issue we have added a menu for the old Sphinx button which contains the new "Build Cronjobs" tool. This tool will ask you to input the path to your sphinx.conf file and will then provide the proper cronjobs based on the applications installed. Furthermore, the tool will also warn you about a possible wrong path as you can see in the screenshot below.

blogentry-126321-0-20229100-1299689622_t blogentry-126321-0-99157900-1299689619_t


Export Tool for Developers

Currently the information.xml file included in the xml folder of each application needs to be written manually, we have now included a tool that allows developers to easily create such file from the ACP without having to write it manually.

blogentry-126321-0-75965500-1299081167_t

This is an example of the file that will be exported from the Members application:


Please note that the option "disabledatinstall" will always be 0 by default unless a previous information.xml file is available and it contains a different value which will be retained. The same goes for the templates, you need to add them manually but as long as you have them in a previous xml file the export function will keep them in the new one as well.


Conclusions

As you can see from the previous screenshots we have not only added new features but also the layout of the pages has been updated as well for better usability, for example you'll notice that the applications not installed are now listed on a column on the right instead of at the bottom where it was harder to see them.



Feel free to comment on this blog entry below or, if you have feedback unrelated to this blog entry, start a new topic in our feedback forum. Be sure to check the What's New in IP.Board 3.2 topic for a running list of announced changes!

<?xml version="1.0" encoding="UTF-8"?>

<information>

	<data>

		<name>Members</name>

		<public_name>Members</public_name>

		<author>Invision Power Services, Inc.</author>

		<description>Manage members and groups</description>

		<disabledatinstall>0</disabledatinstall>

		<global_caches/>

		<website/>

		<update_check/>

		<templategroups>

			<template match="exact">skin_messaging</template>

			<template match="exact">skin_mlist</template>

			<template match="exact">skin_online</template>

			<template match="exact">skin_profile</template>

			<template match="exact">skin_ucp</template>

		</templategroups>

	</data>

</information>

Sign in to follow this  
Followers 0


15 Comments

Posted

Interesting :) Thanks

  • Loading...

Share this comment


Link to comment

Posted

10 loving it
20 loving it more
30 loving it forever
40 goto 10

  • Loading...

Share this comment


Link to comment

Posted

Happy to see my idea accepted by IPS!

Nice improvement.

  • Loading...

Share this comment


Link to comment

Posted

I love the tab permissions.

  • Loading...

Share this comment


Link to comment

Posted

Would be great to be able to add more tabs... a way to customize the menus.

  • Loading...

Share this comment


Link to comment

Posted

The admin cp is looking much more user friendly.

I just hope the main forum changes will be equally as user friendly, since they'll be used by everyone else.

  • Loading...

Share this comment


Link to comment

Posted

Regarding the 'Application Tab Permissions' section, a lot of apps already have a group setting coded into them indicating which groups can access the application. It would be nice if we could select a group setting (just give us a list of columns from the groups table) that indicates whether a member has application permission and show/hide the tab based on that.

It would save us from having to code something into our upgrade scripts to convert the group setting to this new tab permission system.

AlexJ, Adriano Faria and VioAdmin like this
  • Loading...

Share this comment


Link to comment

Posted

Thank you so much for simplifying the method for exporting applications, I always hate compiling my applications.

  • Loading...

Share this comment


Link to comment

Posted

[quote name='Michael' timestamp='1299963176']Regarding the 'Application Tab Permissions&' section, a lot of apps already have a group setting coded into them indicating which groups can access the application. It would be nice if we could select a group setting (just give us a list of columns from the groups table) that indicates whether a member has application permission and show/hide the tab based on that.It would save us from having to code something into our upgrade scripts to convert the group setting to this new tab permission system.

You got it wrong Mike, the setting is only for the TAB visibility and peoples will still be able to access it even with the tab hidden, applications will still need a setting to limit which groups can use it.

  • Loading...

Share this comment


Link to comment

Posted

Now will we be abile to move tabs on the public view so we can order our tabs the way we want them?

  • Loading...

Share this comment


Link to comment

Posted

[quote name='teraßyte' timestamp='1300014900']
You got it wrong Mike, the setting is only for the TAB visibility and peoples will still be able to access it even with the tab hidden, applications will still need a setting to limit which groups can use it.
I don't understand, surely I would want to hide the tab for groups who can't access the app. I mean, I guess one could set it up so that the tab is visible for people who can't access the app, then they get an error message when they do so, but that seems like a bad user experience to me.

IP.Board doesn't show things like the Report Center link to people who can't access the Report Center, so why show a tab to people who can't access the tab's application?

  • Loading...

Share this comment


Link to comment

Posted

[quote name='Michael' timestamp='1300038784']I don't understand, surely I would want to hide the tab for groups who can't access the app. I mean, I guess one could set it up so that the tab is visible for people who can't access the app, then they get an error message when they do so, but that seems like a bad user experience to me.

IP.Board doesn't show things like the Report Center link to people who can't access the Report Center, so why show a tab to people who can't access the tab's application?

I'd tend to agree with you if that was a new function added but that's how it works right now, I merely expanded the "hide tab" option to support groups. If I suddenly change how it works (so that members can't access the application anymore) everyone would need to update their setup causing even more confusion.

  • Loading...

Share this comment


Link to comment

Posted

[quote name='teraßyte' timestamp='1300094464']
I'd tend to agree with you if that was a new function added but that's how it works right now, I merely expanded the "hide tab" option to support groups. If I suddenly change how it works (so that members can't access the application anymore) everyone would need to update their setup causing even more confusion.
What you're adding is a new function, what I'm suggesting just adds on to the same concept. Before, it was a global on/off whether to show the tab. You're now adding an option that lets you show the tab for selected groups. What I would like to see in addition to that is a dropdown of all columns in the groups table that is also checked against, optionally, to see if the user has access to the application, to determine whether to show the tab.

I understand that you probably have the coding for this wrapping up now, but seeing as how this is the first we're all getting to see that this is being changed, this is the first time anyone has the opportunity to give you feedback on it. You have to expect that someone is going to give you some more ideas based on what's being discussed here, especially since most of this seems to be things that weren't exactly requested by the community very often.

  • Loading...

Share this comment


Link to comment

Posted

We'll take the feedback into account for the next release. For now, the change discussed is a minor enhancement to existing functionality (instead of a global on/off, you can now turn on/off per group). Your suggestion has merit, but I don't think we have time to implement it for 3.2 at present. We will re-evaluate as we move along our timelines.

  • Loading...

Share this comment


Link to comment

Posted

[quote name='Enkidu' timestamp='1299857141']
10 loving it
20 loving it more
30 loving it forever
40 goto 10



Holy crap it's been a long time since I've seen BASIC. LOL

  • Loading...

Share this comment


Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now