.time

Not having javascript enabled is hardly a concern in 2012, I'm afraid.  If you disable javascript, you can expect more than half the web to not work correctly.  It is well accepted these days that users who disable javascript understand this and accept the broken functionality.

TitanKing, on 10 January 2012 - 07:59 AM, said:

Let me assure you that our plans for future development are entirely not based on what our competitors have done or are doing.  Our future development plans are based upon what our customers tell us they need.

GoDaddy needs a user experience specialist bad.

Hello,

Per Rhett's request, I will post my suggestion(s) here.

Nexus is a great product when used as a store front, but the subscription management needs some help. This would be a pretty big re-work, but I bet that it would result in a lot of sales. Basically turning Nexus into a Membership management portal instead of a store front. This might require the need for a completely new addon, but Nexus has most of the framework in place.

As is, Nexus is item driven (i.e. shopping cart style). I've been managing a membership website since 2007. I've used everything under the sun. I 'think' with a little tooling, Nexus could be a very powerful membership management portal. IP suite provides all of the tools needed to run and maintain a membership site, with the exception of a back-end payment/management solution (that's a pretty big exception, lol...). I'll try to explain in 2 basic categories:

1. Subscriptions - a subscription should not be an "item or product". Rather, a subscription should be a controller or group for "items and products". This gets confusing to coders because the "subscription" still needs to be an "item" in the checkout process. Think of a subscription as an advanced "bundle" of items.

Quick example: if we have items 1 - 23 in our system and then we decide to create a new "subscription", we should be able to assign only items "1, 4, 13 and 21" to our subscription. In addition, the "item" creation needs to be more flexible. Using our example, item "4" might be an area on our server (a directory or folder). When the item is purchase or included in the subscription, the member that purchases this subscription would then have access to the assigned directory or folder (i.e. Membership Area on your server). Trying to either use existing IP code to customize the portal pages and/or adding some new hooks to the code, is not realistic for most membership website owners. Unless, item "4" could be a set of pages generated by the "Content" addon. That would make sense.

You already have the features for managing groups (which is also critical to membership management). Each subscription would either create or be assigned to a specific group. This would help with support issues and a ton of other membership related problems.

Bottom LIne - a subscription has to be able to perform all of the following:

• Protect/manage items
  
• Protect/manage web pages and directories
  
• Protect/manage special permissions on the forum (access, permissions, features, etc...)
  
• Protect/manage feeds (yes really, this is huge for membership sites)
  
• Protect/manage a dedicated chat room
  
• Protect/manage calendar events and information
  
• Create or assign a user/member group
  
• Create/update recurring billing (see below)

2. Recurring Payments - This is HUGE. This is the single biggest problem with membership software. The payment side of the script has to be able to "report to" and "report from" the merchant account payment processor. The best way to explain is to use an example. If "newguy" signs up for my "subscription1", I should get a notice via email and in the admin (yes, basic). However, I should have admin options for all of the following per sale:

• Create a custom "thank you" landing page per subscription (the membership area is covered above)
  
• The ability to "upsell" each new sale via a sales funnel during signup
  
• The ability to "upsell" existing members based on time frame, product purchased and product expiry date
  
• The ability to "resell with coupon/discount" anyone that decides to cancel their subscription
  
• The ability to generate coupons that are subscription specific (not a generic 30% off anything coupon)
  
• The member should have access to detailed reporting; payments made, product details, invoice download and the ability to cancel any/all subscriptions from their membership portal.
  
• The admin side needs detailed reporting; payments made (with details), new sales charting, bounce rate from sign-up pages, bounce rate from sales funnel and (this is key for membership sites) projected sales based on active subscriptions.

I that is a TON of feature requests, lol... I'm posting this more as an FYI. The leading membership software is aMember and they do not have half of the features that I just listed. Food for thought... sorry for my typos, lol...

THL, on 25 September 2011 - 08:04 PM, said:

its rather difficult to hook into an encoded product with poor documentation... Just saying.... cant even "see" how the code SHOULD look to do whats needed.... I dunno bout the rest, but I Read code well, learn by doing or from a proper example... which in Nexus is a Fail.

As someone is no doubt already thinking about the next version of ipC, I thought I'd start a wish list topic:

1)  A plugin to build valid xml from custom databases.
2)  A good menu manager section, that can build a menu from page structure and/or allow direct editing of the main menu (a bit like fusion menu (sorry Mat)).
3)  Breadcrumbs that respect page folder structure.
4)  A simple toggle to add a sidebar into a page with content fields for main content and sidebar.
5)  Option for global sidebar.
6)  Styles consistency between the new ckeditor, the bbcode page editor and the new .ipsType style set.
7)  More plugins for board features such as gallery image slider, nexus mini-store.
8)  Drag and drop sorting for custom database records.
9)  Proper google map support for custom databases - it is highlighted in the sales bumph but is damn difficult to do and not supported by IPS.
10)  Multiple attachments in articles as standard (with some nice templates built in).

Please... x

The setting you are referring to was added to reduce bandwidth back in the days when many people were browsing over dialup.  The bandwidth savings this option provides is negligible in this day and age, so the option was removed.

When "Manually Approve All Payments" is set to "Yes" and customer pays, in the Client Area it is still marked as "Pending Invoice". Wouldn't it be nice if there is something like 'On-Hold Invoice"? "Pending Invoice" where actually it is already paid is really confusing to customers and may also result on multiple payments.

Currently we can filter our search in IPS Marketplace down to the need for either  IPB, blogs, gallery, IP downloads, IP content, Nexus, and Extra.  Which is nice, but I'd like to take it 1 step further and be able to filter through version number compatibility.

Nothing is more disappointing or frustrating than not knowing right away, if a modification or style is compatible with the software version you are currently using....... Unless I actually read the full description and this provided, if the author even included that information (such details should be mandatory).

It would be really nice if I could simply click a button or something and narrow my search and filter out modification and styles which may not be compatible to the software I am using.  Thus only bring up to view what is compatibly with my current version.

.time, on 02 July 2011 - 10:47 PM, said:

I'll make sure that gets patched for you tomorrow. Sorry for any inconvenience.

Hi, IPS,

please reanable the latest files hook on this forum! i dont like going to marketplace just to see if theres anything new.

Remove it.

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.

Staff, please respond with your remarks after reading.

1) For customers, it would help if they were shown an enhanced shipping page that outlined the title, cost, and shipping duration of their preferred shipping method. If the shipping method is titled "Ground Shipping," that's all that they will see. That does not provide enough details. Customers should be shown some type of block design where they can see nice visuals of their options. No shipping options are shown either, for example: the customer could request insurance at X additional cost or tracking for Y additional cost. There should also be notification if their shipping method comes with tracking already and nexus should email the customer the tracking number after the admin has provided it to them. Likewise, this should be made available in the customer's client center. ( this leads to better transparency )

2) For admins, it would help if shipping methods could be categorized into folders. There can be 5 shipping methods all titled "Ground Shipping" but could be specific to certain products based on weight, size, etc. Since Nexus does not currently support an API-based shipping calculator that connects directly to shipping providers (e.g., USPS, UPS, etc.), at least provide admins an easier way to manually categorize their shipping methods.

Thank you

*facepalm*