Myr

We will be releasing an "actual" app, yes (you will download it from the app marketplace, not from us).  We had one in the past and decided to overhaul it from the ground up taking a different approach, and that app is currently in heavy development.

I see.
To be honest, I would have expected Nexus to handle the subscription part, not PayPal.  It seems to be a case of trying to prevent admin user error, but in this case it's at the expense of what is, from my point of view, an essential feature.

To be fair, I am only starting to run a subscription-based service, so perhaps I am missing something.  But from a consumer's standpoint, all of the subscription websites that I belong to (or have belonged to) offer this feature.
Flickr, web hosting, deviantArt, Livejournal, etc. If they offer recurring billing, it's not normally though PayPal's recurring feature, but a full credit card processor.  Instead, the most common payment method is "X for 1 month, or Y for 3 months, or Z for 12 months", but this is non-recurring billing.  Buying another subscription automatically stacks it onto your current subscription time.  Once your subscription time runs out, you receive notification that it's going to expire, but if you don't purchase a new subscription, it simply expires and they won't bill you again.
As a consumer, I would expect that any site offering subscriptions would allow me to stack my subscription time.

Congratulations on a job well done. I really like the improvements you guys are making within the internet communications industry. IPB is really looking like the best forum out there, especially with such a nice suite available.

Hmm, I wonder how IP.Nexus can accommodate an intuitive checkout process for amazon affiliates. Amazon should have some sort of API-developer feature. oh look here, I found it

https://affiliate-pr...etail/main.html

This definitely seems doable and awesome at the same time.

IP.Board 3.0.x and Applications: End of Life Announcement

So that we can focus all of our development, support, and service efforts on the newest version 3.1 platform and create a great version 3.2, we are announcing the end of support (sometimes called end of life or EOL) for the following IPS software versions (and earlier versions):

• IP.Board 3.0.x
  
• IP.Blog 2.1.x
  
• IP.Gallery 3.1.x
  
• IP.Downloads 2.1.x
  
• IP.Content 1.2.x
  
• IP.Chat 1.0.x

Technical support, installations, and services will end for these products on June 1, 2011. On that date all technical or service requests will be advised to simply upgrade to the most recent versions of the products. We will not force upgrades but will also not be able to diagnose issues or answer questions relating to the older software. Also, on that date, IPS will no longer address any new issues or bugs reported in the older software versions.

You are of course free to continue using these older versions if you wish but IPS will no longer provide assistance after the EOL date.

Security Updates

In the event an issue is discovered impacting the security of these older versions of the software, IPS will provide a patch posted in our announcements forum. We will continue to provide security updates for several months after the EOL date based on severity of the issue.

Internet Explorer 7 Support

The next version of Internet Explorer, version 9, will soon be reaching a final, supported release from Microsoft. Once Internet Explorer 9 final is released we will begin phasing out support for Internet Explorer 7 which will then be two versions behind. This will not be an abrupt end of support but we will base our phase-out of support based on the market share and adoption rate of IE8/9 versus IE7. Issues reported that are specific to IE7 will be evaluated on a case by case basis and, depending on the severity of their impact, we will still address them. However, as a general practice, cosmetic issues or minor lack of functionality specific to IE7 will not be addressed.

We were recently inspired to write up our own year end review of 2010 to go over the highlights of all the accomplishments our staff made during the year. It's also a great overview of the advancements IPS constantly makes for our customers. Here are the highlights:


December 2009

We began blogging about IP.Board 3.1 and IP.Content 1.2. Everyone was very excited to start revealing the upcoming changes to IP.Board and to further the maturing of the new IP.Content product.

January:

• IP.Chat 1.0.0 released as final. IP.Chat 5 user room provided for free to all customers with an active support contract.
  
• Blogged about expected updates to our addon applications
  
• Released public phpdoc documentation for developers
  
• IP.Downloads 2.1.0 released final. IP.Downloads 2.1.0 provides friendly URLs, upload progress bar, multiple files per record, interface updates, and more.
  
• IP.Content 1.2.0 released final. 1.2.0 provides WYSIWYG editors, better control over fields, and better support for attachments.
  
• Gallery 3.1.0 released final. 3.1.0 introduces album cover images, friendly URLs, sub albums, profile picture albums, friendly only albums, and fancy slideshow.
  
• IP.Blog 2.1.0 released final. 2.1.0 includes support for group blogs, Blog This!, RSS imports, resource improvements and more.
  
• Continued blogging about IP.Board 3.1 improvements

February:

• Improvements to spam monitoring service.
  
• Continued blogging about IP.Board 3.1.0 and addon application updates to be expected
  
• Extended our demo system to 48 hours (extended to 5 days later in the year).

March:

• IP.Board 3.1.0 revealed to the community via updated company forums. New features include profile customization, link sharing, status updates, twitter integration, reputation viewing, ad codes, notification system, soft deletions, and more.
  
• Continued blogging about expected application updates and IP.Board 3.1.0 changes.
  
• Skin Generator service launched for free to all active license holders.

April:

• Community Hosting improvements were made allowing for free 20 user chat rooms, IP.Content available for only $5/month, and a switch from generic metrics to user-based limits.
  
• Continued blogging about application updates, and released betas of the new versions for the community to begin testing.
  
• IPS Staff is excited to hear the news that Nakisha Thomas, our Director of Customer Service, welcomes the birth of her son.

May:

• iPhone app developed and released for free to the community.
  
• Skin generator service updated.
  
• Introduced IP.Nexus as our new business platform.

June:

• IP.Board 3.1.0, IP.Gallery 3.2.0, IP.Blog 2.2.0, IP.Downloads 2.2.0, IP.Content 2.0.0, and IP.Chat 1.1.0 released. Many great improvements for all products available to customers - check out the release topic for a full list. It's impressive!
  
• IP.Board 3.1.1, IP.Gallery 3.2.1, IP.Blog 2.2.1, IP.Downloads 2.2.1, IP.Content 2.0.1, IP.Chat 1.1.1 released. Quick bug fixes for the most notable issues in the newest version.
  
• iPhone app updated to support push notifications, amongst other features.
  
• Community directory launched to allow customers free exposure to anyone using the iPhone app or browsing our company forums for any site.
  
• New IPS web site launched.

July:

• IPS conducts a donation drive for Autism research, in part to test our newest upcoming product IP.Nexus, and in addition to raising $1000 via donations from our community, IPS donated a matching $1000 to AutismSpeaks.org.
  
• IP.Board 3.1.2, IP.Gallery 3.2.2, IP.Blog 2.2.2, IP.Downloads 2.2.2, IP.Content 2.0.2, and IP.Chat 1.1.2 released. In addition to important bug fixes, this release includes enhanced SQL error display, ACP live search improvements, SQL toolbox enhancements, improvements to partial member registrations, and more.
  
• Forum support launched allowing official support via our company forums.

August:

• Website improvements to make documentation searching easier and better documentation organization.
  
• Community hosting improvements implemented.

September:

Continued blogging about upcoming updates to our software. IPS does not release roadmaps as they are too easy to stray from and you end up making promises you cannot keep which we never want to do. Instead, we post blog entries when we complete a new feature so everyone knows it's not just a mockup or an unfulfilled hope.

October:

• IP.Board 3.1.3 released.
  
• Skin generator updated and improved.
  
• Release schedule for our products announced. The first and last time IPS has done this!

November:

• IP.Nexus 1.0.0 released.IP.Nexus is our powerful ecommerce solution that allows you to monetize your IP.Board easily.
  
• IP.Content 2.1.0 released. Features include external widgets, redesigned default interface, block variable help, admin interface improvements, better forum integration, template import/export, and more.
  
• IP.Nexus 1.0.1 released. As part of our commitment to maintain and update Nexus regularly, we release our first update for Nexus only 10 days after initial release of 1.0.0.
  
• IP.Content 2.1.1 released. Resolves bugs reported since the release of 2.1.0.
  
• IP.Board 3.1.4 released. This release includes new like and comment functionality which our other application updates will be making use of.
  
• IPS Marketplace goes live. The Marketplace allows developers to sell their IPS product addons directly through our site, reaching more customers with less hassle.
  
• IP.Nexus 1.0.2 released. This release is part of our continuing effort to ensure any issues affecting your ability to monetize your site using IP.Nexus are promptly addressed.
  
• New release and quality assurance testing two-stage procedure implemented to help enhance quality assurance of releases, and to give customers a chance to test and use the software prior to actual release.
  
• IPS Staff is excited to hear the news that Lindy Throgmartin, our CEO, welcomes the birth of his son.

December

• In just a couple weeks of activity already paid out over two thousand dollars to Marketplace contributors.
  
• IP.Blog 2.3.0 released. 2.3.0 includes new like and commenting systems, Facebook like buttons on entries, tweet entry button on entries, a redesigned portal interface, improved notifications, new interfaces, and more.
  
• IP.Downloads 2.3.0 released. 2.3.0 includes IP.Nexus integration for selling downloads, an overhauled user interface, improved notifications, new like and comment system integration, and much more.
  
• IP.Nexus 1.0.3 released.

Still to come: Maintenance releases, new IP.Chat version, and IP.Gallery 4.0 reveal!



We are all looking forward to a productive 2011 and will continue to bring you the best community software around!

I am wondering if it is possible to make packages where money goes directly to another paypal account. I want to sell other members products, but I want the income to go directly their paypal and not my paypal that I've set in Nexus settings.

1. I want each packages to have an option to what paypal mail the money should be sent to.
2. I would like to take let's say 10% of each sales, after all, I am hosting the sellers package.

I want this system because I just want to give my users the platform to sell, I don't want the payments to go through my email when it's not one of my products I'm selling. I am trying to avoid customers coming to me  with "failed delivery, support and so on" when this should be taken care of the seller himself and not me (the host of pack). Thanks in advance, hoping for some answers here .

I appreciate Matt and the team have their own plans and are probably well on their way with 3.2, but here's what I'd like to see for CycleChat:

• View new content - Show what is actually new (unread) content; show topics only (as opposed to multiple posts from the same topic).
• Hover preview (really liking the new version) - To work on forum view, all search results, and personal conversations - with ACP options for trigger time, and post-hover fade time.
• Thread marking - to mark up to where I have actually read in a thread, rather than marking the whole thing as read. (Matt has said this is on the list - yippee! )
• Lighter CSS - There's tons of the stuff ... can it be made lighter by making more "global" style attributes (with the option of adding custom code if needed)?
• Better editor - I've lost count of the number of "issues" people have had with the post editor. Hopefully some improvements for 3.2? Emoticons as a pop-up perhaps?
• Simple alerts, likes, and trophies - Not strictly an "everyman" feature set, but after playing with xF this is something I think would greatly improve member-engagement at my site.
• Simple out-of-the-box Article system - IP.Content is great, but confuses the hell out of me. I just want a simple, categorised, article system where I select from a pre-built template, apply my site "style" as a wrapper, and then start adding articles.
• Expiring notifications - Once I've read a message, remove the notification about it.

I'm sure I can think of others, but that's not a bad start for now.

Cheers,
Shaun

This is something really boring and extremely repetitive. Every time we install a hook, we have to navigate to Edit Settings, click thousands times until you get the settings for the specific hook. It gets worst if you have several hooks installed.

One simple thing would be to add HOOK SETTINGS in Manage Hooks, right here:



The idea is to centralize everything in one area, save time!

Please consider this!

After much deliberation:

- I have scoured Bing's TOC and I must admit they are much less restrictive. They allow local caching of data and are less concerned in general in how you access and store the information. They do have limits of 500,000 requests in a 12 month period but with caching of data this shouldn't be a huge problem. For these reasons, I have switched to Bing for the default mapping service.
- I have abstracted the mapping into IP.Board core and abstracted out the services into separate classes so you can write your own mapping plug ins to use Google, etc.

As a long time webdeveloper and webdesigner that have worked with Wordpress for the last 5 years or so I see some issues with IPC and from the response I see here this is shared by others as well and this is why IPC is not more successful than it is, despite being an excellent product.

The biggest problem with IPC is that out of the box it does not behave like most database applications like Wordpress and article managers. The Articles feature would be ideal for blogs or content sites like articles, knowledgebases and so on, but the strange navigation issues makes it confusing and annoying rather than easy and logical. The archive system is an interesting way of handling things, but it does not work practicly and it does not mimic any system I have ever seen...and I have seen alot.  This makes articles confusing and annoying to work with. The fact that you can only have one set of articles also makes this feature limited instead of inspire creativity.

Databases are awesome in so many ways and where the archive system for the articles fail, databases work perfectly. The big problem with databases is almost identical with articles, meaning that navigation is a pain in the...if you want to build anything but a list since the categories template is built as a list and it's not exactly straight forward to change that layout to a design like found for the articles.

In both cases the breadcrumb completely ruin the navigation experience to the point where its completely useless to use the wrapper, especially since the wrapper comes with a huge CSS file which you probably never will use and which will only make your website slow for no good reason.

Without good examples on how to add different designs and implement different functions for both the Articles system and the Databases IPC is failing in my opinion.

With a few good examples to work from and with the possibilty to remove the confusing navigation quirks in the Articles this would change dramaticly. Rework the breadcrumb issue so it makes sense and work on a separation of necessary code in the header so that the CSS is slimmed down for only what is needed for the wrapper with options to add more CSS individually in each file rather than dump it all in wether you need it or not...well, then you have a real winner here!

Wordpress has an equally complicated system if you want to diver deep into it, but there each function has it's own page with examples and I often return to those for ideas and examples to wok from and this is something I deeply miss for IPC.

Keep up the good work and I look forward to see IPC rise to new heights

Mark -

Ok... the teasing blog entries are all great but it's getting to be too much of a taunt.    

How about an update on when we expect to see this and when we can purchase it.
I was ready to put my money down more than a month ago.

Thanks for any update!

For a while now I have been wanting to write up something to say "Hey, Love IPS and the direction it is going in". But, in better words and a deeper description.

Instead, I'd just like to point out how nice it is to roam around the forums and see things like: steady progress, nice useful enhancements, team support & encouragement, member support & encouragement, kindness, etc.

Keep up the good work! Thanks to all...

I agree. I've said it many times too. I don't care about the notification. Why are you taking me to the notification? The notification holds nothing relevant. It did its job when it popped up. Take me to what the notification is notifying me about.

The thing that is annoying me is the notification about a status update does not have a link to the person's status just a link to the notifications settings so I keep accidently going to the notification settings when I want to pull up the status.