Charles

Well... you're getting into fuzzy territory here :)

It usually depends on where you're hosted/company is registered. We don't go policing content on our client sites of course.

I don't have a firm answer for you on that one.

Yes that actually just changed this evening :)

For those asking about IP.Content on another domain, keep in mind that www.invisionpower.com is powered by IP.Content

With canned replies, I mean standard reply texts, that you can insert into posts, PM, etc.

Regarding wiki; I currently use a native wiki system: i.e. wiki articles in posts. Its an important part of my site.

You can sort of do canned replied with multi-moderation.

If your Community Suite goes on sale, I'll probably jump off the vb ship. ;)

Check announcements forum :)

I think it's because the little sidebar is a hook Matt made as a demo one day that people liked so much we included it :) Not to say we can't do that as some point of course...

http://forums.televisionwithoutpity.com has like 10 million posts (or something like that) and is owned by NBC

http://life.atlantafalcons.com/index Atlanta Falcons has 2 million

For big boards specifically for search we suggest Sphinx wherever possible. It's supported as standard in IPB3.

For templating you could always get one of our demos and have a click around :)

is there anything in your terms and conditions that guarantees that the 6 monthly support renewal will be offered for lifetime licenses?

Of course who knows in the distant future but it would be very hard for us to change the way we structure our renewals. The 6 month renewal allows us to not only offer support and upgrades but also addon services like spam monitor (and some future ones we're planning) at no extra cost.

We don't have that specific permission level in your example however there are others that we do have.

The permissions you mentioned are for forum-level permissions. There are also individual settings in each forum settings (outside permissions setup) and at the user group level.

Personally, I don't buy "in the next week or two" promises. I've learned my lessons from experiences. :o I am more like "I will believe it when I see it" kind of person.

Well then be sure to read our blog tomorrow and hang around here for the next few weeks ;)

Mark here at IPS (handles most conversions) would be the best person to answer your question. I am sure he will see this topic tomorrow or you can email sales and ask and we can get you a proper answer.

I still have an active license of a Vb and I have to say that it's really chaotic in licensed customer forum right now at Vb. There is no way that I am going to renew my vb license in current status. I am not paying a dime to those backstabbing bastards at Vb.

And so-called manager has vanished ever since the new pricing has been announced and left few support staffs to deal with the mess. What a day.

FYI, I had two active Vb licenses. I moved one of my Vb license to IPB in May 2008 and still retain one active Vb license.

There are huge differences in Vb3 and IPB3. But, to be bluntly honest, I never rely on mods because they are always unreliable. But if you do use lots of mods, I will say that Vb will be better for you.

Though some of really important and much-needed Vb mod features are built right in IPB as official features.

Oh, and IPB has an official CMS, Gallery, Downloads, and Blog (Which I am not so fond of.) as add-on.

As for mods we are working on things to encourage more mods but, keep in mind, we have lots of features standard in IPB (like certain SEO functions and such) that require a mod for vB. So one could say you need fewer mods in IPB depending on what you're after.

New versions of Gallery/Downloads/Blog/etc. are in the works. We will be posting blog updates about it in the next week or two :)

Just a reminder: we appreciate the feedback (both positive on how we can improve) on our products but let's not become vB trolls. They have enough problems right now and if IPS were to ever have trouble we would expect a similar professional courtesy from them.

Done :)

If we run a promotion it would be for anyone - not just vB converts. There are plenty of other products out there :)

We are happy to keep a topic like this open if it does not turn into a bashing thread. We are out to offer a great community solution here and we appreciate our customers being quite happy with our products but don't want things to turn dark in the process :)


As for alternatives to addons perhaps you can post a list of which ones you are looking for alternatives? I am sure the community can give you pointers.

We are seriously considering a sale either in the license or the conversion services. In the last 24 hours between posts on the forums and in our sales email people are clamoring for something of the sort.

I think it's perfectly reasonable to lock tickets that have had no activity for over 5 days. Honestly no one has ever complained or even really noticed before :) Everyone just starts a new ticket if needed.

It's not like we are denying support to anyone - just trying to keep things tidy. We added it because people would reopen tickets sometimes months old by replying to an old email or something and it would get confusing.

Your instance is rare I would think. Most clients would not take more than 5 days to reply. If they do not reply it's almost always because ticket is resolved so the system automatically marks that status.

Tickets only auto-locked (resolved) if, after one of our staff replies, you do not make a new reply in 5 days.

It keeps people from reopening ancient tickets.

Can you provide a ticket number where you waited that long during business hours?

CSS Changes:

/public/style_css/master_css/ipb_styles.css

ul.post_controls { - background: inherit url(../../style_images/master/gradient_bg.png) repeat-x 50%; + background-image: url(../../style_images/master/gradient_bg.png); + background-repeat: repeat-x; + background-position: 50%; font-size: 0.8em; text-align: right; padding: 6px 10px 28px 6px;

I will post the list of changed files since 3.0.3 but we do suggest you simply upload all files. There are so many changed files we could have easily missed some from the list.

---

• admin
• applications
• core
• js
• ipb3CSS.js
• ipb3Replacements.js
• ipb3TemplateSandR.js
• ipb3uAgents.js
• modules_admin
• ajax
• css.php
• hooks.php
• livesearch.php
• templates.php
• applications.php
• hooks.php
• setup.php
• diagnostics
• diagnostics.php
• manage_languages.php
• logs
• errorlogs.php
• warnlogs.php
• dashboard.php
• posts
• badwords.php
• bbcode.php
• emoticons.php
• media.php
• mssql.php
• system
• taskmanager.php
• skinsets.php
• tools.php
• tools
• cache.php
• login.php
• performance.php
• rebuild.php
• settings.php
[*]modules_public

[*]applications [*]languages [*]mycp [*]sql [*]templates

• ajax
• facebook.php
• findnames.php
• attach
• attach.php
• register.php
• reports
• reports.php
• search.php
• usercp
• manualResolver.php
[*]setup

[*]global [*]search

• versions
• install
• sql
• core_mssql_tables.php
• core_mysql_tables.php

upg_10002

version_upgrade_mysql.php

[*]upg_30001

• mssql_updates.php
• mssql_updates_1.php
• mssql_updates_4.php
• mysql_updates_5.php
• version_upgrade.php

upg_30003

mssql_updates.php

[*]upg_30010

• mssql_updates.php

skin_cp

cp_skin_adminlogs.php

cp_skin_applications.php

cp_skin_diagnostics.php

cp_skin_help_files.php

cp_skin_modlogs.php

cp_skin_system.php

cp_skin_templates.php

cp_skin_tools.php

[*]sources

• classes
• attach
• class_attach.php
• plugin_msg.php
• plugin_post.php
• reportLibrary.php
• reportNotifications.php

reportPlugins

blog.php

• admin_core_language_pack.xml
• core_bbcode.xml
• core_lofi_css.xml
• core_lofi_templates.xml
• core_mediatag.xml
• core_root_css.xml
• core_root_templates.xml
• core_settings.xml
• core_tasks.xml
• core_xmlskin_css.xml
• core_xmlskin_templates.xml
• public_core_language_pack.xml
• versions.xml

forums

app_class_forums.php

extensions

• furlTemplates.php
• searchDisplay.php
• searchPlugin.php
• acp.forums.js
• modules_admin
• attachments
• types.php
• forums.php
• moderator.php
• multimods.php
• rss
• export.php
• import.php
• stats.php

[*]js [*]forums [*]statistics

modules_public

ajax

• topics.php
• stats.php
• forums
• announcements.php
• boards.php
• markasread.php
• topics.php
• moderate.php
• post
• post.php

[*]setup [*]extras [*]moderate

• versions
• install
• sql
• forums_mssql_tables.php
• forums_mysql_tables.php

skin_cp

cp_skin_forums.php

[*]sources

• classes
• digest.php
• forums
• admin_forum_functions.php
• class_forums.php
• moderate.php
• post
• classPost.php
• classPostForms.php

• admin_forums_language_pack.xml
• forums_lofi_templates.xml
• forums_root_templates.xml
• forums_settings.xml
• forums_xmlskin_templates.xml
• hooks
• recent_topics.xml
• watched_items.xml
• public_forums_language_pack.xml
• versions.xml

members

extensions

• furlTemplates.php
• usercpForms.php
• bulkmail
• bulkmail.php
• groups
• groups.php
• banfilters.php
• customfields.php
• members.php
• ranks.php
• reputation.php
• tools.php

[*]modules_admin [*]members

modules_public

ajax

• card.php
• dst.php
• rate.php
• view.php
• online
• online.php
• friends.php
• view.php

[*]list [*]profile

skin_cp

cp_skin_banfilters.php

cp_skin_bulkmail.php

cp_skin_groups.php

cp_skin_member.php

cp_skin_reputation.php

cp_skin_tools.php

[*]sources

• classes
• messaging
• messengerFunctions.php

tabs

gallery.php

posts.php

topics.php

• messengerSearch_mssql.php

xml

admin_members_language_pack.xml

members_lofi_templates.xml

members_root_css.xml

members_root_templates.xml

members_settings.xml

members_xmlskin_templates.xml

public_members_language_pack.xml

versions.xml

• ips
• blog
• extensions
• coreExtensions.php
• furlRedirect.php
• furlTemplates.php
• portalPlugins
• blogs.php
• usercpForms.php

modules_admin

cblocks

• manage.php
• custom.php
• headers.php
• groups
• manage.php
• rebuild.php

[*]customize [*]tools

modules_public

actions

• forward.php
• findblogs.php
• display
• archive.php
• blog.php
• trackback.php
• post
• mod.php

[*]setup [*]ajax [*]external

• versions
• install
• sql
• blog_mssql_fulltext.php

upg_14004

mssql_updates.php

[*]upg_14006

• mssql_updates.php

upg_20000

version_upgrade.php

• cp_skin_blog.php

sources

lib

• entry_add_cblock.php
• entry_edit_entry.php
• entry_new_entry.php
• entry_reply_entry.php
• lib_blogfunctions.php

[*]xml

• admin_blog_language_pack.xml
• blog_lofi_css.xml
• blog_lofi_templates.xml
• blog_root_css.xml
• blog_root_templates.xml
• blog_settings.xml
• blog_xmlskin_css.xml
• blog_xmlskin_templates.xml
• public_blog_language_pack.xml
• versions.xml

calendar

extensions

• portalPlugins
• calendar.php
[*]modules_admin

[*]rssOutput.php

• calendar
• calendars.php

modules_public

calendar

• calendars.php

[*]skin_cp

• cp_skin_calendar.php

xml

admin_calendar_language_pack.xml

calendar_lofi_templates.xml

calendar_root_css.xml

calendar_root_templates.xml

calendar_settings.xml

calendar_xmlskin_templates.xml

hooks

• board_index_calendar.xml

[*]public_calendar_language_pack.xml [*]versions.xml

• modules_public
• ajax
• update.php
• parachat
• chat.php
[*]skin_cp

• cp_skin_chat.php

xml

admin_chat_language_pack.xml

chat_lofi_templates.xml

chat_root_css.xml

chat_root_templates.xml

chat_settings.xml

chat_xmlskin_templates.xml

public_chat_language_pack.xml

versions.xml

• modules_admin
• customize
• cfields.php
• mimetypes.php
• tools
• bulkimport.php
[*]modules_public

• ajax
• comments.php
• post
• submit.php
[*]setup

• versions
• upg_20000
• version_upgrade.php

skin_cp

cp_skin_mimetypes.php

cp_skin_tools.php

[*]sources

• classes
• categories.php
• cfields.php
• storage
• url.php
[*]xml

• admin_downloads_language_pack.xml
• downloads_lofi_css.xml
• downloads_lofi_templates.xml
• downloads_root_css.xml
• downloads_root_templates.xml
• downloads_settings.xml
• downloads_xmlskin_css.xml
• downloads_xmlskin_templates.xml
• public_downloads_language_pack.xml
• versions.xml

gallery

extensions

• admin
• group_form.php
[*]modules_admin

[*]coreVariables.php [*]searchPlugin.php

• cats
• manage.php
• groups
• manage.php
• manage.php
• postform
• postform.php
[*]modules_public

[*]media

• cats
• list.php
• post
• image.php
• stats.php

[*]stats

setup

versions

• install
• sql
• gallery_mssql_inserts.php
[*]upg_30000

• version_upgrade.php

skin_cp

cp_skin_gallery.php

[*]sources

• libs
• lib_categories.php
• lib_gallery.php
• lib_imagelisting.php
• lib_notifications.php

xml

admin_gallery_language_pack.xml

gallery_lofi_css.xml

gallery_lofi_templates.xml

gallery_root_css.xml

gallery_root_templates.xml

gallery_settings.xml

gallery_xmlskin_css.xml

gallery_xmlskin_templates.xml

public_gallery_language_pack.xml

versions.xml

• modules_admin
• portal
• portal.php

xml

admin_portal_language_pack.xml

portal_lofi_templates.xml

portal_root_templates.xml

portal_settings.xml

portal_xmlskin_templates.xml

public_portal_language_pack.xml

versions.xml

• subscriptions
• modules_admin
• subscriptions
• manage.php

setup

versions

• install
• sql
• subscriptions_mssql_tables.php
• subscriptions_mssql_uninstall.php
• subscriptions_mysql_tables.php

• classes
• classGateway.php
• subsLib.php

xml

public_subscriptions_language_pack.xml

subscriptions_lofi_templates.xml

subscriptions_root_templates.xml

subscriptions_settings.xml

subscriptions_xmlskin_templates.xml

versions.xml

• userAgents.php

js

acp.hooks.js

acp.languages.js

acp.livesearch.js

acp.menu.js

acp.tabbed_basic_editor.js

acp.templates.js

[*]setup

• applications
• install
• sections
• install.php

upgrade

sections

• upgrade.php

• base
• ipsRegistry_setup.php

templates

skin_setup.php

[*]xml

• config.xml

skin_cp

acp_editor.css

cp_skin_global.php

[*]sources

• base
• core.php
• ipsController.php
• ipsRegistry.php
• classes
• bbcode
• core.php
• custom
• defaults.php
[*]class_localization.php [*]class_reputation_cache.php [*]class_taskmanager.php [*]customfields

• profileFields.php

editor

class_editor.php

class_editor_rte.php

[*]facebook

• connect.php

itemmarking

classItemMarking.php

[*]member

• memberFunctions.php

output

adminOutput.php

formats

• html
• htmlOutput.php
[*]publicOutput.php

• sphinxIndexPlugin.php

session

publicSessions.php

sso.rename.php

[*]skins

• skinCaching.php
• skinFunctions.php
• skinImportExport.php

useragents

userAgentFunctions.php

• han_email.php
• han_login.php
• han_parse_bbcode.php

loginauth

convert

• auth.php
• auth.php
• live
• acp.php
• auth.php
• loginauth_install.xml
• loginauth_install.xml

[*]external [*]login_core.php [*]openid

template_plugins

tp_date.php

tp_striping.php

tp_url.php

• blog
• colorpicker
• Slider.js
• slider.js

• converge_local
• converge.php

• interface
• blog
• apis
• server_blogger.php
• server_metaweblog.php
• xmlrpc.php

public

• js
• ipb.js
• ipb_blog.js
• ipb_bloglist.js
• ipb_blogxml.js
• ips.attach.js
• ips.board.js
• ips.editor.js
• ips.post.js
• ips.topic.js
• ips.ucp.js
• skins
• setsData.xml

[*]resources

style_css

master_css

• ipb_styles.css

• ips_kernel
• ClassApiServer.php
• ClassConvertCharset.php
• ClassDb.php
• ClassDbMysql.php
• ClassDbMysqlClient.php
• ClassDbMysqliClient.php
• ClassEmail.php
• ClassTemplateEngine.php
• db_lib
• mysql_tools.php

It might be a good idea, maybe after the authors has been notified of problems with there hooks/mods. To put out some kind of info post showing other moder's sections of which was coursing problems and how to fix it for future reference and also how to improve our coding for the future.

cap

We were going to post our list but we want to contact the authors first. Don't want to make people look bad for a simple little bug :)

We are making a list of mods with known issues and we will definitely be contacting mod authors to see if they can optimize the mods.

We are developing one for a client now and hope to provide it in a future release of IPB.

I think this topic has devolved into a debate on the various ways one can document software products :) let's not start a huge argument about the merits of one over the other. We all agree documentation is very important and it is being actively worked on.

As IPB3 is so new we are still writing many of these documents. Anyone who has written documentation knows it is extremely time consuming. We actually have quite a bit written already in various areas that has been written over time and as things come up. We are currently working on pulling all that various information together into centralized guides. You may have noticed the new Resources area on our community here and the new capabilities of IP.Content 1.1 - we will be using those new features for our core documentation.

We have, basically, two approaches:

ACP Inline Help: This talks about the specific page you're on without having to leave the admin area. It's not to explain in great detail just to explain the overall functions of the page you're on.
Guides: A traditional article on various subjects.

The guides will have various subjects and take information beyond what the straightforward ACP Inline Help can provide. Examples may include:

• Basics of skinning
• Moderation guide
• Creation applications/hooks
• Creating a single-sign-on bridge between IPB and your applications
• Template logic
• etc.
  

Much of this is already written in the form of articles on the resource site and the many dozens of PDFs our development and support departments have written since the launch of IPB3. I am personally organizing all this varied information this week into a logical approach (quite an undertaking I might add). We will begin publishing these various documents in the next few days and continuing to expand upon them quite frequently over the next couple months.

Documentation is very important to us as it is to you. Taken another way, good documents reduce the number of tickets we receive which is good for both our clients and for us. Plus, it eliminates the need for topics like this which end up going in circles with people who, at a base level, do agree with each other. :)

It does not have read/write separation at this time but it's something we have experimented with and may make it into a release of IPB in the future.