Jump to content

  2. → Viewing Profile: Likes: RObiN-HoOD

RObiN-HoOD

Member Since 22 Dec 2004
Offline Last Active Yesterday, 09:16 PM
-----

#2259407 IP.Board & The Forum Will Be Dead Within 5 Years

Posted Matt on 25 April 2012 - 02:29 AM

Quote

I agree that facebook was mostly social talk. But not anymore. Facebook is changing and they are improving their groups step by step. Their groups are now turned into social groups with many features and on topic discussion. Facebook is pushing members to join their groups, by allowing anyone to add others to groups. It does not beat forums in discussion functionality yet, but it surely will get there.

Quite the opposite actually. We've been approached by at least two heavy Facebook brands who have or want to switch to IPB because they've outgrown their Facebook page. They cite that it's hard to interact directly with fans and that it's impossible to search for content or look at older content.

I expect this trend to continue as companies use Facebook to build a brand and then look to expand it outside of Facebook.


#2167832 Post Edit History - REALLY NEED THIS

Posted Con on 09 September 2011 - 02:35 AM

I can't find this in the marketplace. This is a very useful potential feature that would prevent many board issues (loss of incriminating evidence e.g. due to staff members gone astray, irrecoverable important information, etc.). I'm sure if someone created a mod for this they would get paid handsomely for it.

Ideal features include (but are not limited to) the following:
  • capability for unlimited number of history entries of any size (obviously within external limits) recorded in raw BB&HTML.
  • accessible regardless of whether the "edited by" line is displayed (e.g. could be a simple link on the bar at the top of the post).
  • records all edits, regardless of whether the "edited by" line is displayed.
  • editor username, IP, and edit date/time are recorded for each entry.
  • ability to restrict groups/users that are able to view the history.
  • ability to restrict forums and groups/users that the history is used on.
  • can be enabled/disabled (but simply disabling it will not clear entries).
  • the capability to clear entries both individually and by bulk (ideally using manually-defined parameters) in order to conserve space.
  • ability to revert post content to that of a previous entry, and have the reversion recorded as a new entry - not crucial since this can easily be done with Copy&Paste.
  • a post comparison feature (see vBulletin or Wikipedia for examples) - again, this is not crucial since comparisons can easily be done externally e.g. via Notepad++.
If anyone has any further ideas for features please chip in.

It would be great to see this feature implemented ASAP, if not as a stock feature then at least as a mod.


#2146275 Disallow permanent deletion

Posted nrep on 03 August 2011 - 03:06 AM

I'd like to make another suggestion for future forum versions. It would be great to disallow the permanent deletion option for super mod/admin usergroups. I never totally remove any content from my forums, so that there's always some sort of audit trail or record of the post - and I'd like to be able to enforce this option so that it also applies to super moderators. I'm sure a global or usergroup option to disallow hard delete would be a simple addition :).


#2139520 IP.Board 3.2.0 and Applications Released

Posted IPS News on 25 July 2011 - 09:27 AM

Invision Power Services, Inc. is pleased to announce the release of IP.Board 3.2.0 and its Applications!

Everyone at IPS is very proud of IP.Board 3.2.0 and the Application updates. We have worked hard to create a quality, modern community platform and the feedback from our clients has been tremendous.

We are releasing the following new software:


IP.Board 3.2.0
Fully featured community platform including forums, members profiles, calendar, status system, integration, and much, much more.


IP.Gallery 4.1.0
Categories and photo albums for your members to share their images and videos on your community.


IP.Nexus 1.3.0
Fully featured commerce system to sell products, membership access, advertising, digital downloads, and more. Includes tools like a support desk to help manage you clients.


IP.Blog 2.4.0
Allow you and your members to post blogs on your community or syndicate externally hosted blogs easily.


IP.Downloads 2.4.0
Complete file management application including file version control, commenting, and forum topic linking.


IP.Content 2.2.0
Content management for your community - run a full web site or a simply community portal. The possibilities are endless.


IP.Chat 1.3.0
Engage your members in real time chat or send them private chats while in the chat room.


IP.Calendar 3.2.0
Event calendar for your community with multiple calendars, public/private events, and iCal support.


Release Notes

Though IP.Board 3.2.0 and its applications have been tested for months, you never know what you are going to get when thousands of people start using it overnight. Therefore: now that IP.Board 3.2.0 and the applications will be used by a much larger audience we will probably come across many as yet undiscovered bugs. You can expect maintenance releases for all the software frequently as we work quickly to address any issues reported.
  • We are now providing technical support and services for IP.Board 3.2.0 and the applications. As you might imagine, many thousands of clients will be asking for help so please note that if you request upgrade or install assistance that there could be a delay up to a few days to process that request.
  • If you choose to use our auto-installer/upgrade service in the client area we appreciate your feedback as this is a new service.
  • If you are upgrading a community with a large number of posts you may wish to have your web host execute the post table alter query on your behalf. Large post tables may time out running this query in the browser. The upgrade system will warn you if this is needed. As a benchmark, our install of 865,000+ posts took a bit less than 3 minutes to run this query.
  • Your skin will of course need to be redone after you upgrade to 3.2.0.
  • The visual skin editor in 3.2.0 should still be considered a beta feature. It will be improved with each maintenance update.
  • Each of the applications specified above is only compatible with IP.Board 3.2 and not older versions (for example, IP.Nexus 1.3 cannot be installed on IP.Board 3.1.x).
  • We may reply to this topic with hot-fix patches or notes if any critical issues come up so please use the "Follow this Topic" feature to get notified.
  • If you experience any problems, before submitting a ticket, please disable all third party applications and hooks.


What's new in IP.Board 3.2!

In addition to this list there are countless other minor improvements and changes based on client feedback too numerous to mention.


Calendar Improvements
Moderator Functions
New Text Editor
AdminCP
Core Functionality

Miscellaneous Changes
  • "Delete All" button has been added to the SQL error logs page
  • Linear+ and Outline modes removed for topic viewing (they're a hold-over from an older time on the web and it's time to retire them)
  • Support for IPv6
  • You can now use the member management tools to search for incomplete members
  • Pagination added to the incomplete members page of the ACP
  • If only one skin or language is choosable, the dropdown selector at the bottom of the page will be hidden
  • Member photos and member avatars are being merged into one function: member photo. There was too much overlap between the two features.
  • IP.Calendar and IP.Chat will no longer be bundled in the IP.Board download zip to reduce the size of the download. This also allows clients who have no interest in IP.Chat or IP.Calendar to choose not to download or install those applications. Of course those who do wish to use those applications can easily download from the client area and install them.
  • Rebuild FURL cache button has been moved to the cache management page.
  • It is now possible to rename the "hooks" folder to something else editing the constant IPS_HOOKS_PATH in initdata.php.
  • You can now edit each group's report center permissions directly from the group management area
  • Report center now supports item marking to remember and indicate which reports you've viewed
  • Customers who have purchased Copyright Removal no longer need to enter a separate Copyright Removal key. The copyright will automatically be removed when activating your license.
  • New settings for attachments to limit size of files stored on disk
  • Separate ACP restriction options have been added for managing spam users and incomplete users (access to these areas were previously controlled by the option "can manage banned users").
  • "Show X Last visitors in profile" now shows always the last 5 visitors if the setting is enabled rather than having a 3, 5, 10 dropdown choice.
  • New ACP tool to create the cronjobs to rebuild sphinx indexes
  • When adding a ban filter in the ACP you will now have an option to enter a reason visible to all admins (the reason won't show in the public side).
  • Pinned, polls, and moved topic prefixes have been moved to language files (they were previously in the settings area)
  • Many redundant or pointless settings removed. Other settings moved to more logical locations. Some settings groups merged to create fewer groups to go through when setting up your community. System Settings menu item moved to a top-level menu item under System tab so it's available with one-click anywhere in AdminCP.
  • The note box in your My Settings (UserCP) area has been removed. It is a hold-over from years past and doesn't seem to make sense in community software. If you are one of the very few people who use this: make a copy of your notes before upgrade.
  • The unread topic marking system will now remember what page of a topic you left off reading rather than assume you read the entire topic on the first click.

IP.Nexus 1.3.0 IP.Gallery 4.1.0
http://community.inv...-41-dev-update/




Other Applications

Other applications have been updated to work with IP.Board 3.2.0, have received cosmetic improvements, and other minor updates to improve functionality. All applications will get larger updates now that IP.Board 3.2.0 has been released. Keep an eye on our news feed for information.

Code-Level Changes

These are changes made at the code-level of our software during this release phase that may interest our power-user clients.


Performance Improvements
  • Reduced several cache-load queries on the ACP index page
  • Combined two permissions queries loaded on every ACP page into one
  • Added some additional cache-loading calls to other ACP pages (manage applications, manage hooks, manage members)
  • Added some caching for fetching the max version ID in the upgrade_history table, which reduces the number of queries on the ACP manage applications page by the number of applications installed
  • Changed how modules are grabbed when IN_DEV is enabled for menu building (runs one query instead of one query per application)
  • class_forums was getting loaded and initialized twice in the Manage Forums page - fixed so it's not reloaded a second time. Also removed a shortcut for the class in the manage forums file to reduce small amount of overhead/memory.
  • Removed a query for group data on Manage Forums page (group_cache is already loaded, so used that instead)
  • Removed several deprecated functions, reducing the size of some classes and reducing their resulting overhead
  • Edited language export routine (for IN_DEV mode) so that it only exports the data we absolutely need. This reduces the size of our language XML files significantly, and also reduces memory overhead needed to process the language XML files.
  • Index added on ibf_posts.post_parent to speed up certain update queries that previously required a full table scan
  • A lot of unused code in the friend management files has been removed
  • Avatar or profile photo cleanup tools in ACP were unnecessarily loading and instantiating upload class
  • Removed outdated/non-functional coloring in admin logs
  • Calendar has been rewritten, and much unused code has been removed.
  • Caches used by calendar were not being properly loaded at runtime
  • Changed most of the file_exists call in the code with is_file for a faster code execution
  • The bbcode cache now uses the ‘bbcode_tag’ field as array key instead of an incremental integer, that allows a faster data access for single bbcode tags as there is no need to scan the whole array with a foreach.
  • An unnecessary query has been removed from the forum index view (the query used to verify the name used for the friendly URL is correct)
  • Removed unnecessary query from report center report view
  • A cache used by report center was being queried separately instead of at page initiation
  • Report center plugins are now cached for quicker runtime lookup without having to query the database
  • Useless queries removed from report center
  • Some queries that selected all rows and counted them (instead of running COUNT style queries) were changed to be better optimized
  • ACP skin files previously extended the output class unnecessarily. This was removed, resulting in approximately 20KB or more memory savings in each ACP page.
  • Report center plugins are now cached for quicker runtime lookup without having to query the database
  • RSS import now is much faster on boards with lots of feeds setup in the ACP.
  • overWrite header query / method_exists moved from every page load and value is cached in app_cache



Developer-Oriented Changes
Changes that may impact resource authors and skinners (including removed functions, database changes, new hooks, etc.)
  • $this->DB->force_data_type has been removed. Mod authors should now call $this->DB->setDataType( $column, $type ) instead.
  • $this->DB->no_escape_fields has been hidden. You should use the available $this->DB->preventAddSlashes( array( 'col' => 1 ) ); syntax instead.
  • Login management custom configurations have moved to database handling. conf.php (or conf.dist.php) files are no longer needed (though acp.php still is).
  • search_results, sessions.location, and cache_store.cs_extra are all removed
  • If you have a findIpAddress extension you can now add an array of additional columns to pull from your table as the fourth array member. i.e. "'posts' => array( 'author_id', 'ip_address', 'post_date', array( 'pid' ) ),"
  • IPB will now do a better job of cleaning up centralized application data during uninstall, so applications don't have to do it manually. (http://community.inv...support-ticket/)
  • The way hook data to-be-exported is stored has changed. This should have minimal impact on developers as the upgrade routine will update it for developers. This should make working with hooks between multiple developers easier, and make hooks import, export, install and uninstall in a much more consistent manner whether IN_DEV is on or not.
  • Many skin system bugs have been resolved, and improvements implemented, making the skin system more flexible to developers using it outside of normal contexts, while allowing it to be more forgiving of various formatting possibilities (i.e. typehinting for function parameters and spacing around function parameter definitions).
  • Central permission management now correctly can handle more than one permission type within a single application
  • IPv6 is now supported. You should ensure any database columns holding IP addresses are varchar(46) or larger.
  • You should use the new ipsRegistry::getAppClass( $app ); call to load your app_class_(application).php class. This ensures any library hooks execute as appropriate and consolidates duplicative code.
  • You should use the new constants IPS_FILE_PERMISSION / IPS_FOLDER_PERMISSION for file and folder permission values. i.e. instead of chmod( $file, 0777 ); use chmod( $file, IPS_FILE_PERMISSION ); instead.
  • Calendar has been completely rewritten - the DB schema has changed, dates are stored as datetime parts in MySQL, etc.
  • The ACP has a new interface implemented, some of the JS has changed, jQuery is now supported in the ACP
  • Removed 4 data hooks in public_forums_forums_topics: topicViewTopicData, topicViewDisplayData, topicViewForumData, topicViewPostData. All 4 of them can be replaced with a simple skin overloader for the template "skin_topic > topicViewTemplate".
  • Photos and avatars have been merged.
  • Photos thumbs are now cropped at 100px and you can select which area to crop
  • Twitter / Facebook photos are actually imported and re-sized where possible (needs fopen URL wrappers otherwise the thumb URL for the services is used)
  • Some functionality for importing/exporting/rebuilding from and to XML files has been hidden unless IN_DEV mode is enabled
  • Added a second parameter for the function “$this→cache→getCache( $CACHE_KEY, FALSE );” which allows to skip the loading from the database if the cache isn’t loaded already.
  • A new option to define an application when creating an hook, if the application is filled the code checks if it is enabled and if not skips loading the hook file completely.



    class_forums::fetchTopicFolderIcon() has been changed to return an array of meta-data about the topic that can be used to generate the topic icon, although Rikki is changing how topic icons work in general anyways.
    pp_*thumb*_x is now pp_*small*_x
  • The sessions API (admin/sources/classes/session/api.php) now supports a different cutoff time rather than the default one, additional joins, ‘where’ query bits, complete ‘where’ query part override.
  • The function “IPSLib::unpackGroup()” now is “IPSMember::unpackGroup()”.
  • ACP group_form.php plugins now support an optional third method: postSave(). This method accepts one parameter (the group ID), is only called if present, is called after the rest of the group data is saved, and should not return anything.
  • Added a getCount() method to the like class to return just the number of followers
  • The setting disable_reportpost has been removed. Our applications now check the report center permissions directly, instead.
  • Hooks Improvements: http://community.inv...s-improvements/
  • Applications Improvements: http://community.inv...s-improvements/
  • A new extensions file per-app is supported: permissionsSync.php. Class name should be “(app)PermissionsSync” and supports a constructor (ipsRegistry reference passed) and one method with no arguments: updatePermissions(). This method can be used to rebuild application caches when the app permissions have been updated from the central permission manager.
  • Deprecated function getBlogID() in the blog API has been removed, developers will need to use the more updated function fetchBlogIds()
  • makeProfileLink, memberViewImages, makePassword, makeNameFormatted, canReceiveMobileNotifications have been moved to IPSMember
  • unconvertSmilies has been moved to IPSText. The redirect method in the bbcode class has been removed.
  • The “doneScreen” method in the admin output class has been entirely removed. Authors are encouraged to use the global_message/silentRedirectWithMessage() methodology instead.
  • The “redirect” method in the admin output class now simply routes to silentRedirectWithMessage(), and is marked deprecated.
  • The template “global_main_wrapper_no_furniture” has been removed from the admin skin.
  • Function “rebuildSphinxConfig” has been moved from “IPSLib” to “admin_core_applications_applications”
  • classCommunication.php was removed, and classFileManagement.php was extended to handle POST requests (encompassing the only functionality missing compared to classCommunication.php)
  • Almost all private methods have been switched to protected to allow more robust hook capabilities
  • New pagination potions to use a next/previous style pagination. Next/previous style pagination supports AJAX pagination.
  • The column “ban_nocache” has been removed from the “banfilters” table.
  • New adminOutput method setMessage() has been added. Allows to set the global_message, and allows to specify a “sticky” flag or not.
  • ACP Settings are now in their own “settings” module and the templates have been moved as well in “cp_skin_settings”.
  • menu.xml files for ACP modules now support specifying a language key, which can then be placed into “(app)_admin_menulang.php” as “menu__(language_key)” to support menu language abstraction in the ACP. This is optional for apps.



#2135248 3.2 Feature Suggestion: Option to close poll automatically

Posted joelle on 18 July 2011 - 03:11 AM

Quote

"Do not close this poll if there is a tie"
This would be a nice addition to my suggestion. :)


#2088766 3.2 Feature Suggestion: Option to close poll automatically

Posted chilihead on 09 March 2011 - 07:47 PM

+2

I need this for web contests I run. The members vote, and then there is a winner, but I can't close the poll. I need to close the poll but not the topic, so they can discuss, but not vote after it is over.

That is the most important, but to take it a step further, the option:

"Do not close this poll if there is a tie"

With this option it would close upon the tie breaking vote.

Thanks


#2088236 3.2 Feature Suggestion: Option to close poll automatically

Posted joelle on 08 March 2011 - 03:05 PM

How about adding the option that polls can be automatically closed after a certain time frame?

Posted Image


#2128067 Tag auto-completion for 3.2

Posted KT Walrus on 26 June 2011 - 03:00 PM

Any chance that tag auto-completion could be implemented before the 3.2 release?

I've been playing around with the new tag system to see if I should use it for my site.  I would like to be able to have auto-completion as the user types in a tag name, so that there is a greater chance that people use the same tags as often as is appropriate.  I don't want users to be confused as to whether to use the plural of a tag name or some alternate spelling,  The autocomplete suggestions would like the most frequently used tags that match the typing first.  

Without autocompletion, I think I might have to go with a closed tag system where I have to list all appropriate tags for the forum, but I don't like this since it may be limiting and harder to maintain.  Better to allow users to make up their own tags.  I also don't know how good an interface this would be if I listed 100 or more possible predefined tags.

I think it might be better to have a big list of predefined tags, but have the option to do tag completion within the closed system.  So, the user would be shown the preferred tags to use but still be able to type in new ones not in the list.  Then, if I could moderate the new ones and decide to add them to the predefined list, then I could better control the tags used and still allow the users to request new tags to be added.

Anyway, the input of the tags just doesn't seem to be as finished as it should be to end up with good tags that can be used to find all related topics.


#2121790 Integrate moderation with ModeratorCP

Posted martin-al on 12 June 2011 - 01:22 PM

IP.Downloads needs a better integration for moderation of new downloads.
Users can submit downloads to the system, but needs to be approved by moderator+.

However, moderators need a better way to be noticed about it, rather then have to visit the Moderation-area in IP.D. all the time.

-> Integrate it with the new Moderator CP in IP.Board 3.2.0
-> Send a notification to moderators upon new submission.

:)


#2077395 IP.Blog ... Some Much Needed Features!

Posted Drakior on 06 February 2011 - 10:40 PM

These are the kinds of features that would help bring IP.Blog a little bit more up to speed.  While IP.Blog plays nicely with the whole community suite, and the integration is awesome, as a blogging system, it's sorely lacking in some very key areas that many basic blogs out there presently enjoy.

These are just the basics that are missing:

  • Assign an Image to an Entry
    Like any blog out there on the internet, every entry has an image associated with it.  This image is shown as part of the teaser.  IP.Blog presently does not parse any image code while displaying teasers so there's no elegant alternative.  And enabling full html to all users is not an option.  IP.Blog's basic entry listing is just text and an avatar.  Not very exciting, not very interesting.  Allowing users to put a little thumbnail of an image for each entry would go a long way to make this look like a "real" blog.
  • Some basic user customization
    Give the users the ability to do basic customization to their blogs, namely the ability to upload a custom header image/logo, with size restrictions set by the admin.
  • Easily re-order entries
    An elegant solution to allow blog entries to be reordered, at the very least some kind of inline "quick edit" to modify post dates if that's all that can be done.
  • Sorting options throughout
    The option to sort posts by date (asc/desc) throughout the blog engine.  For example, when viewing Archives, it just sorts by date DESC with no other option.  Just as a blog reader, options to filter through content need to be added.
  • Custom fields
    Allow admins to add custom fields so that we can parse, sort and order blog entries using our own criteria.
There's lots more that could be added and improved upon, but these few things would go a long way to bring IP.Blog a little bit more up to speed.  

I don't expect IP.Blog to compete shoulder to shoulder with years-long established systems like Wordpress.  And IP.Blog has done some really great things with forum/community integration, so please give some IP.Blog users some love!  We will now have over 1200 IP.Blog bloggers in my community, so please consider some updates soon!

Thx!


#1932843 Marking Topic Creator

Posted Tanax on 27 March 2010 - 02:10 AM

I don't know if this has been discussed before, but isn't it kind of convenient to mark the topic owner's posts within a thread? Perhaps a symbol in the postbit, or something to make it easier to know that "he/she created this topic". Instead of having to go back to the first post to see it(or topiclist in worst case).

I know it can be done via modification, but I think it's a handy feature that should be built in :)


#2094913 [FEATURE REQUEST] Soft delete in IPD

Posted Tanax on 25 March 2011 - 09:58 AM

View PostAdriano Faria, on 25 March 2011 - 06:33 AM, said:

hey RObiN-HoOD, sorry, I don't understand what's the real need for this in IP.Board... isn't it the same of UNAPPROVE a file (a topic/post in IP.Board) ?

No. Unapproving content means that the content yet hasn't been approved by a moderator. Soft-delete is deleted content but the content is still in-line so that it's easier to restore, backtrack topics, etc.

For instance, if moderator X unapprove a topic to hide it, how would moderator Y know that the topic isn't waiting for approval but rather that the topic is just hidden? This could perhaps be dealt with on smaller boards by a sticky with links to all hidden topics in the staff area but for boards with a large amount of activity this is simply not possible which was why soft-delete was developed in the first place.


#2076512 What's new in IP.Board 3.2.0 and related Apps (so far)

Posted Charles on 04 February 2011 - 08:41 AM

In our spirit of keeping everyone up to date, this topic will serve as a running list of what's new in IP.Board 3.2.0. As we make changes we will update this topic so check back now and then. This is not yet a complete list as we are still making changes, adding new features, and doing other work. If you don't see what you're looking for here just yet please check back later!

As always with IPS, everything listed here is not part of a "possible" roadmap. We will only post items on this list when they are 100% complete and included in IP.Board 3.2.0 so you can trust that what we post in public is what you will get.

Calendar Improvements

Moderator Functions

New Text Editor

AdminCP

Core Functionality


Miscellaneous Changes
  • "Delete All" button has been added to the SQL error logs page
  • Linear+ and Outline modes removed for topic viewing (they're a hold-over from an older time on the web and it's time to retire them)
  • Support for IPv6
  • You can now use the member management tools to search for incomplete members
  • Pagination added to the incomplete members page of the ACP
  • If only one skin or language is choosable, the dropdown selector at the bottom of the page will be hidden
  • Member photos and member avatars are being merged into one function: member photo. There was too much overlap between the two features.
  • IP.Calendar and IP.Chat will no longer be bundled in the IP.Board download zip to reduce the size of the download. This also allows clients who have no interest in IP.Chat or IP.Calendar to choose not to download or install those applications. Of course those who do wish to use those applications can easily download from the client area and install them.
  • Rebuild FURL cache button has been moved to the cache management page.
  • It is now possible to rename the “hooks” folder to something else editing the constant IPS_HOOKS_PATH in initdata.php.
  • You can now edit each group’s report center permissions directly from the group management area
  • Report center now supports item marking to remember and indicate which reports you’ve viewed
  • Customers who have purchased Copyright Removal no longer need to enter a separate Copyright Removal key. The copyright will automatically be removed when activating your license.
  • New settings for attachments to limit size of files stored on disk
  • Separate ACP restriction options have been added for managing spam users and incomplete users (access to these areas were previously controlled by the option “can manage banned users”).
  • “Show X Last visitors in profile” now shows always the last 5 visitors if the setting is enabled rather than having a 3, 5, 10 dropdown choice.
  • New ACP tool to create the cronjobs to rebuild sphinx indexes
  • When adding a ban filter in the ACP you will now have an option to enter a reason visible to all admins (the reason won’t show in the public side).
  • Pinned, polls, and moved topic prefixes have been moved to language files (they were previously in the settings area)
  • Many redundant or pointless settings removed. Other settings moved to more logical locations. Some settings groups merged to create fewer groups to go through when setting up your community. System Settings menu item moved to a top-level menu item under System tab so it's available with one-click anywhere in AdminCP.
  • The note box in your My Settings (UserCP) area has been removed. It is a hold-over from years past and doesn't seem to make sense in community software. If you are one of the very few people who use this: make a copy of your notes before upgrade.
  • The unread topic marking system will now remember what page of a topic you left off reading rather than assume you read the entire topic on the first click.


Other Important Changes
  • IP.Subscriptions, our simple application to allow you to sell member group promotions on your community, will be updated to work with IP.Board 3.2 but this will be the last update to IP.Subscriptions. IP.Subscriptions has been around for many years - long before communities were assumed to bring in revenue - and it's time to retire it to focus on our more modern application: IP.Nexus. With the release of IP.Board 3.2, IP.Subscriptions will be considered end of life (EOL) and will no longer be supported. Clients should switch to the new IP.Nexus product which is continually updated and contains many more opportunities to monetize your community. A member of our community, Andy Rixon, has agreed to take on continuing development of this product so those of you who use it will still have a solution.
  • The Portal application in IP.Board has existed from the very early days of our company. It was only ever intended as a simple portal and demo of the software but grew a bit over time. It has had minimal updates and the feature set is very minimal when compared to today's expectations of community owners and operators. The Portal application will not ship with IP.Board 3.2 and should be considered EOL. It will be available in the IPS Marketplace after IP.Board 3.2's release for those of you who do use it so you can still upgrade to 3.2. We will also post information on how to easily replicate the Portal's functionality in IP.Content which offers all that the old Portal did and much, much more. A member of our community, Andy Rixon, has agreed to take on continuing development of this product so those of you who use it will still have a solution.
  • As IP.Board 3.2 will have a whole new default skin, the CleanCut skin will become redundant and will therefore no longer be updated by IPS.



#1951047 Track a Member

Posted alistairgd on 10 May 2010 - 05:26 PM

In the case of a troublesome member, it would be neat to get a notification each time they post, making it possible to track their behavior without going to the formal stage of post moderation and the approval system.

In operation this would be appear as a "Track this member" option appearing in their profile but only visible to Moderators.

I've often wished something like this was available.


#2029773 Copying threads

Posted ikillbill on 15 October 2010 - 12:50 AM

indeed that why this feature that has been asked for many times still unavailable? lol




  1. Invision Power Services
  2. → Viewing Profile: Likes: RObiN-HoOD
  3. Privacy Policy
  4. Community Rules ·