$this->library = new $classToLoad( $this->registry ); $this->library->setPermissionData(); $posts = $this->library->getPosts( array( 'postType' => array( 'sdelete', 'pdelete', 'oktoremove' ), 'sortField' => 'post_date', 'sortOrder' => 'desc', 'parse' => true, 'getCount' => true, 'limit' => 10, 'offset' => $st ) ); $total = $this->library->getPostsCount();

		$classToLoad	= IPSLib::loadLibrary( IPSLib::getAppDir('forums') . '/sources/classes/topics.php', 'app_forums_classes_topics', 'forums' );

Yes, that's really it. The library is quite flexible and should aid you in converting your modifications to 3.2, reducing duplicate code in your modifications, and reducing potential bugs with your code, especially as new features are added to IP.Board moving forward.


In Closing...

We have spent some time consolidating moderator tools and making them easier to understand and easier to use for IP.Board 3.2. All of the pages you see in the screenshots above allow third party applications to easily plugin to them so that even your third party applications can be managed from this single interface (note that third party applications can also add their own sidebar tabs, should they have moderator tools that do not fall under the existing generic categories). Also, while this was not discussed above, moderators will only see and be able to access tabs that they have permission to access. In my screenshots I am logged in as an admin/super moderator so I can access all tools, but the IP address tools (for instance) will not show to regular forum moderators. As new moderator tools are made available in IP.Board, we now have an obvious home to place them so you'll never have to hunt them down in the software again.

We hope you like these changes, and that they make managing your site easier than ever!


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!

• Issue a new warning (or warning reduction)
• Edit the member's profile details
• View stored warn logs and notes
• Add a new note to the member account
  

• Most users are not going to know your permission configurations and would become confused hearing that content they shared is viewable by some but not others
• As mentioned, users can simply download files and upload elsewhere to link to, or copy and paste the destination contents
• Complicated permission checking routines would negatively affect the page loading speed, as there are more resources needed to verify all of the different permission permutations possible across all applications
• Content caching would potentially cause issues with shared content. While we could account for this in our applications, it would be more difficult to account for this in third party applications that can also utilize this new system.
  

• Improving the experience
  We've been accused in the past of having a 'clunky' experience in some areas, so we've worked hard to improve the user experience in key areas. Some of these are usability changes, while others relate to reducing clutter on the screen or relocating elements.
  
• Making the skin easier for 3rd party developers (and ourselves!) to use
  Another focus was on making our skin - particularly the CSS - easier to use, for skinners, developers, even our own team. We've found that as new features were added, whole blocks of existing CSS were copied, pasted, then tweaked to suit the new feature. This creates some resource overhead, not to mention more work for skinners and developers. To remedy this, we've begun introducing a new approach to our CSS: more modular units that can be reused and combined easily to make many interfaces easy to implement. This will be gradually introduced throughout the skin as areas get updated in future point releases. Already, we've been able to remove large sections of old CSS as the updated areas make use of the new modular CSS.
  
• Modernizing the display
  It's been 3 years since we first began working on IP.Board 3.0, and the internet has come some way since then. We decided it was time to refresh the visual style of our default skin. While it will still be clearly recognizable as IP.Board, we've added some polish to the overall style, and made more use of technologies such as CSS3.

• Global wrapper
  This is probably a given, since it influences the rest of the skin. Parts have been made more streamlined, with a new member & moderator bar, a new application bar that now supports as many apps as you choose to install, inline sign in and more.
  
• Forum view
  While the basic concept of listing topics inside a forum hasn't been altered, we've made big updates to the presentation, including rethinking the display of non-essential items and a new, friendly topic preview.
  
• Topics view
  As with forum view, the basic structure has not changed (familiarity is a good thing!), but numerous elements have been tweaked, changed, and tidied. All in all, reading topics should be a more pleasant experience for your users.
  
• Profile
  Our profile view was in need of overhauling, so that's what we've done! It now sports a vastly cleaner display while keeping all the relevant information accessible. Data from 3rd party apps is easily incorporated without fear of breaking the tab bar as in 3.0. In addition, we have merged profile comments and status updates, giving members a modern 'wall' in their profile.
  
• Calendar
  We've previously posted blog entries about new features you can expect to see in Calendar, and to go along with that, we've completely revamped almost every aspect of the calendar display - hopefully making it a more inviting place for your community to share events.
  
• Registration
  We identified some time ago that our registration routine was less than optimal, especially when considering communities that make use of IP.Nexus, with its ability to sell packages at registration. To remedy that, we have rethought the registration routine, to present Nexus packages in a better way, get rid of unnecessary steps along the way, and above all make it quicker for your prospective members to register
  
• Moderation
  We will elaborate on this point at a later date, but we have made the various day-to-day moderation tasks easy to access and use - a boon for your moderating team.
  
• View New Content
  Our View New Content area has steadily grown more complex as additional sorting and filtering options have been introduced, so we felt it was time to improve the display of those options to make it all a bit easier to use.
  
• Posting Screen
  We've updated the new topic/reply screen to be more streamlined, as well as integrate some new goodies that we'll talk about later.
  
• Redirect Screens
  The old-fashioned 'you are being redirected' screens are now a thing of the past. Every area has been updated to use a new inline notification display, which doesn't get in the way and fades after a few seconds.
  
  

<?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>

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!

1|http://www.google.it/

Additionally IP.Board 3.2 will now add also the IP.Board long version in the update URL together with the hook long version, in this way the update script can return only 1 for older versions or add also the new 'update url' variable for IP.Board 3.2+:

IP.Board 3.1: http://www.domain.com/checkHookUpdate.php?hookKey=test_hook&version=10000

IP.Board 3.2: http://www.domain.com/checkHookUpdate.php?hookKey=test_hook&boardVersion=32000&version=10000

Install a New Hook

As you may have already noticed from the screenshot above the "Install a New Hook" form is now a tab and you won't need to scroll down to the bottom of the page anymore, especially when you have a large list of hooks installed.




Conclusion

Many other small tweaks and optimizations have been implemented in the layout as you can see from the screenshots and also in the code, finally all the enhancements discussed above are available in the Hook Details page as well which contains a summary of everything concerning the hook.





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!

• You can upload an iCalendar file (which will usually have a .ics extension) through an upload form
• You can define feeds (using http://, https://, or webcal:// protocols) to import on a regular basis
  

• IP.Board 3.2.0 Dev Update: Calendar Improvements, Part I: SEO Improvements
• IP.Board 3.2.0 Dev Update: Calendar Improvements, Part II: Consistency
• IP.Board 3.2.0 Dev Update: Calendar Improvements, Part III: RSVP
• IP.Board 3.2.0 Dev Update: Calendar Improvements, Part IV: Simplification and Interface Changes