AlexJ

Weppa333, on 25 May 2012 - 02:42 AM, said:

A bit of a bold statement as I see multiquote has been used even in this topic..

This has turned into quite the issue on one of my communities since we started making use of the revamped warning system in IPB 3.3. My moderators and I love being able to force a warned user to acknowledge their warning before they can post again.

But... warned members seem to be almost unanimously confused when the quick editor disappears, and very few of them think to try the "Reply to this topic" button at the top of the page.

The inherent issue here is that our users are so accustomed to using the quick reply box, they don't know what to do or what's wrong when it vanishes upon the receipt of a warning. Cue a private message to a moderator or a status update proclaiming "I can't post anymore! Why?"


I see two ways to address this:

1) Completely block off the user's access to the community until they have acknowledged the warning. E.g.: whenever they try to access anything, put the warning in their face and ask them to acknowledge it. Has the major advantage of being impossible to miss, and keeping users from submitting content to any area of the site until they acknowledge it (what's to stop user warned for swearing excessively on the forums from swearing in the comments of a calendar entry, with the current setup?). And frankly, if a user received a warning, I want that warning to be the very first thing they see next time they visit my site.

2) Display something in the quick editor's place upon the receipt of a warning. Ex.: "You have recently received a warning. You must acknowledge it before you are able to post again." Might work, but it would require a template modification which could prove a hassle for all the skin designers who just updated their 3.2 skins to 3.3. From an administrative point of view, I think this is also less desirable than effectively giving the user a ban that they are able to lift themselves (that's what option #1 accomplishes, in a nutshell).


This seems like a simple UI/UX oversight, but it creates unnecessary work for moderators that can easily be handled by the software with one of the above changes.

AlexJ, on 23 May 2012 - 11:49 AM, said:

Actually in IP.Nexus 1.5 there's a feature whereby users can cancel renewals without needing to raise a ticket

AlexJ, on 23 May 2012 - 11:43 AM, said:

Just as now you can choose not to renew a single addon.

In what way is it complicated? All we are doing is moving IP.Board under the Suite rather than as the root app

I've been wanting this change for SO long!.. Finally be able to run IP.Content solo!

stoo2000, on 17 May 2012 - 01:33 PM, said:

and this is bad - we want to know what was actually done in developer version before release

One thing I'd REALLY like to stress...

A lot of us do NOT want a gallery system that is designed around the idea of it being a PHOTOGRAPHY website.  That's a big part of the problem I have with a lot of the various gallery systems out there.  My membership could not care LESS about f stops, exposures etc.  They want an EASY way to upload, share and reuse images of them and their projects that they can use in discussions on the forums, blogs etc.

They want to come to our site and be able to slice and dice the gallery to find examples of the kind of project they are looking to do so that they can see how different options LOOK.  Having categorized images that are searchable and WELL DESCRIBED on the page is crucial to them being able to find relevant images and also greatly impacts the visibility in the search engines.

James

Ireally like the xenforo image viewer, with mousewheel controls.I hope that IPG will offer similar modern html5 / jquery technology.

I know this is available to mod authors so that administrators can be informed if an update is available. Why not skinners?

I regularly have people e-mail me and tell me my products are 'bugged' or 'flawed' yet in reality, it's because they've upgraded from 3.2 -> 3.3 without downloading the latest version of the skin.

This would be an extremely useful addition in my opinion.

Thanks.

Ok, thought that would be the case.

I think when the White Label app is released, IPS are going to have a lot of work on their hands! By the response of many users, I have seen at least 10 indicate they will be buying the white label app. So at a guess, at least 50 within the first few weeks. So, (for example purposes only) 50x1000=50000.  Bonus for all employees??

wmarcy, on 07 May 2012 - 07:25 AM, said:

signd3's question has already been answered properly, without sarcasm. So I'm struggling to see what you are getting at with that post.

A cost associated with it?  I Can't ask my users to actually buy an app for mobile access.

£1.49?

They are static files and won't be editable via the ACP, language system, etc.  Realistically, we don't even want to have to include them - sadly, not everyone understands how to configure their servers so that they're not needed.

There are quite a few static index.html files with error messages like the following:

<html>
<head><title>IP.Board - Bulletin Board System</title></head>
<body>
<h1>403: IP.Board -&gt; Forbidden</h1>
<hr>
You have reached this page in error, please use your back button to return to the forum.
<hr>
<a href="http://www.invisionpower.com">IP.Board</a>
</body>
</html>

I suggest either (i) making the message universally alterable, e.g. via a language bit, or (ii) implementing a more generic error message that does not suggest any specific site (e.g. invisionpower.com) or software (e.g. IP.Board, bulletin board, forum).