Michael

When you're in a topic and you choose the topic moderation option to delete that topic, you not only get a javascript prompt asking you to confirm this, but upon accepting that you go to a second page where you have to once again confirm you want to delete the topic. Did folks have a problem with the old way, where you only got one confirmation screen? The new way seems like overkill to me.

For being able to make new settings, someone may want to be able to list the different available applications as a menu selection. Much like #show_groups# and #show_forums#.

That would be a suggestion for IP.Tracker, IP.Board has the functionality built in to it to allow this already, apps (like IP.Tracker) just need to tie into that.

Also would be nice if the popup with the differences needs to be closed clicking on the close button because if you click by mistake outside it you need to click again compare differences. (probably you can make this change also in 3.0.1 instead of 3.1 :P )[*]A nice addition in ACP would be to make the same modular thing made for the groups also for the forums, I know a lot of mods out there adds settings to each forum and a system like the one used for the group permissions would help a lot modders.[*]Can you please add 2 more parameters ($lang_file and $app) in the getTemplate function of the hanEmail class? If we use an email template from another file we ned to load it before calling the function and if for any reason the check of the language set by the user fails the board loads the default file with the default language that of course won't have our custom email templates. For now I solved the problem writing my own getTemplate functions but honestly is a bit annoying that I need to copy/paste the same function just to change the template name (I think I have done the same thing for IP.Tracker if I don't mistake :P)[*]Now that you added the small icon to let us know which topic we are tracking in forum view can you also add a link to that image so we can unsubscribe from those topics without opening them one after one? :o (Maybe with some nice ajax code to not reload the page :D)
In the skin editor when you click the button "Compare Differences" the popup is too small, it should open with a bigger size like when you click on the green button on a template tab to work full screen on the template.

We used to have an option on the search page to explain those things like double quotes, + & -, but it seems to be gone now. Maybe restoring that would help folks who aren't aware of this?

We used to have an option on the search page to explain those things like double quotes, + & -, but it seems to be gone now. Maybe restoring that would help folks who aren't aware of this?

I have a small request to make for future updates to IPB (hopefully 3.0.1 :P).

I would like to see the option to change the default post view threshold for members, as discussed here. The default is "Currently viewing all posts", but I would like to be able to change this to a custom threshold of "Hiding all posts below -3 points" by default (or however many points you choose).

This would be a great way for the community to actively moderate topics, by negative voting on unsuitable posts. Once enough negative votes have been made, the post will be hidden. Sort of like "burying" on Digg.

I vote no on this feature. People requesting new modifications will want their own custom smell integration (smelligration?) settings, group permissions, etc. More work for the mod authors.

Nothing will need to be changed, it's not going to remove any member groups you have or move any members to other groups when you upgrade.

Nothing will need to be changed, it's not going to remove any member groups you have or move any members to other groups when you upgrade.

Um, no, that's not profit, that's revenue. That money then has to go toward paying the developers to write new code, the support staff for answering tickets and processing payments, the management who run the company, the ISP for internet access (which definitely isn't cheap for businesses who do their own hosting), and all of the building rent, utilities, upkeep, and maintenance at their headquarters. And even then I'm sure I'm missing something. (Also, on what planet is $140 9100% greater than $49?)

Bottom line, IPS isn't raking in mountains of pure profit from every sale. It bothers me when people forget that there's overhead to software development (says the guy with a grandfathered lifetime license of IP.Board for $129 :whistle: )...

Would it be possible (in a future version, of course, unless it's something you can throw in easily enough) to make the 'report a post' feature use the javascript popup class? If you go into a topic and report the post, when you hit 'back' you get directed back to the page that actually sends the report, and the report gets sent again. If you could just popup a form where you could report the post, the 'back' button will then really go back again.

Maybe I'm crazy, but I thought that the preview board did do it in a popup way back when.

Please say there is new ladies holding laptops :)

+1

Would it be possible (in a future version, of course, unless it's something you can throw in easily enough) to make the 'report a post' feature use the javascript popup class? If you go into a topic and report the post, when you hit 'back' you get directed back to the page that actually sends the report, and the report gets sent again. If you could just popup a form where you could report the post, the 'back' button will then really go back again.

Maybe I'm crazy, but I thought that the preview board did do it in a popup way back when.

According to Brandon, you need to re-import the hook. In your Admin CP, on the System tab, click the 'Manage Hooks' link on the left. Down at the bottom of the page, click the Browse button and browse to the XML file for this hook. You can find it in the /admin/applications/members/xml/hooks/ directory of the IP.Board 3.0.0 files, and it's called 'status_updates.xml'. Just re-import this XML file from there, it should fix this.

Would it be possible (in a future version, of course, unless it's something you can throw in easily enough) to make the 'report a post' feature use the javascript popup class? If you go into a topic and report the post, when you hit 'back' you get directed back to the page that actually sends the report, and the report gets sent again. If you could just popup a form where you could report the post, the 'back' button will then really go back again.

Maybe I'm crazy, but I thought that the preview board did do it in a popup way back when.

As a result of this topic, I'm curious how hard it would be to create the skin changes necessary to display the data how you want. I can't say whether any of that would be available by default with IPB (since I don't control the skinning), but perhaps if we supplied the necessary changes to make the search look the way you are used to, would that be an acceptable compromise? i.e. either through the resource site, or some other similar manner?

I think with maybe 30 minutes tonight of my own time I can come up with something that resembles the 2.x style. I wouldn't want to spend my time doing that if it's not something you'd ultimately be interested in (i.e. if you would only be happy if it is released by default in IPB). That is, just to show you that I'm not ignoring what you're saying, even if I don't agree personally. :)

As do I.

I think it's important for IPS to note that many people are expressing these same views, while I don't know if I've ever heard anyone say they prefer this new way of displaying the data. They shouldn't take the relatively few users who do express their displeasure with the new setup (relatively as compared to their entire user base) as meaning that everyone who isn't saying anything likes the new way. Yes, there are roadblocks to achieving both the multi-tabbed interface and displaying the data we're all used to, but these concerns we've been having have been presented for several months now.

That old running thread on the Preview forum had quite a few posts in agreement with what I (and others) wrote, and my first post in that thread was quite upvoted. I would hazard a guess that the majority of people that regularly use the "View New Posts" function on 2.3.6 see the new "View New Content" results as a downgrade.


Some.


Yes, please do make the results tabular. Overall you guys have done a great job with 3.0, I'm quite confident that you are up to the challenge of properly remedying this issue. This is really the only major sticking point I have with 3.0 and it's a big one (the other being new topic markers, which is somewhat related).


It wasn't broken to begin with and did not need fixing at all.

1) Bring back the columnar format. It's easy to parse, and your eyes know right where to go for each bit of information once you're familiar with the format. The new format uses two "rows" of information for each "new" result and there is plenty of wasted white space. In this particular instance, adding white space for the sake of making the results appear "cleaner" simply doesn't work in my opinion. This goes against the grain "form follows function".

2) The topic title links to the first new post in the thread. Previously, the topic title linked to the first post in the thread and you used the "New Post" icon to go to the first new post. Now there is no way to go to the first post, which is useful if you want to catch up on a thread you haven't viewed in a while (among other reasons). This is completely inconsistent with how the title link works when viewing the topic list in a forum (which itself isn't consistent when viewing the forum index!!)

3) Number of "Views" was removed. Useful to see threads that are particularly active.

4) "Topic Starter" was removed. This is nice information to have, as you may be more interested in threads started by particular users than others. As a forum admin, this is also useful when you want to keep an eye on threads started by particular users (for instance, someone who may be a trouble starter).

5) You can no longer click on the number of "Replies" to get a popup showing the replies in a thread.

6) No attachments icon so you can see threads with attachments in them. This also includes the accompanying link that would give you a popup showing all the attachments (which I have used many times).

7) No means to get to the "Last Post". Currently in 2.3.6, the "Last post by" text links to the last post in the thread. Useful if you want to jump right to the end of a thread.

8) Page links were removed for threads spanning multiple pages. This includes the "Jump to page" link shown before the page links.

9) The "Get active topics for:" dropdown at the bottom of the "View New Post" results is gone. Functionality removed.

As you can see, even with the improvements you've made, there's still quite a bit missing from the original "View New Posts" results. Much of this functionality exists when viewing the topics in a forum. Link to first post in thread, topic starter, attachment link, replies link, link to last post, and number of views are all present, in a nice, columnar format. But the "View New Posts" results as it exists in 2.3, which is nearly identical in appearance, contains too much information? What?

Please bring back the functionality and appearance of the 2.3.6 "View New Posts" results.

..Al

Nice idea.

Remember, this is a "1.0" release of the hooks system. We wanted to keep it mostly simple (but make it as powerful as possible) so that we could gauge what would be useful to both modders and users alike, before going on a rampage trying to incorporate a bunch of things no one would ever use.

We'd also like to give modders a way to handle the updates through the resource site at some point, but haven't worked out details on that yet.

Is that what vbSEO does? That doesn't seem like it'd be worth it. It would have to run all links through something like cURL to fetch the page source and extract out the page title value. That doesn't seem like it'd be worth it to me, but I'm no SEO guru.

Unfortunately, guys, despite the laborious and time-consuming testing we do locally, it's just not the same as testing on a box with hundreds (sometimes thousands) of users online and millions of posts. Basically, this is a real world situation. We need to do real world testing at times.

We'd rather do it here, on our own site, and get IPB3 working as good as we possibly can, than release IPB to you guys with slow functions and so forth. Just look at it this way - we're doing the testing here, where we can control, debug, monitor and fix it, to save you trouble down the road. :)

Maybe you should show the options to Root Admins only then? I just can't help thinking that the current setup is not ideal. On at least two occasions already here on this site, I've had to tell someone that they had to enable IN_DEV just to change the positioning of a hook. Whenever they would do that, all users on the board could either get huge ugly errors or get info revealed to them that they shouldn't have.

It would be one thing if a board admin could have a development board where they did have IN_DEV turned on so they could experiment with this, but even with that setup, once they figure out what needs changed there is still no way other than enabling IN_DEV on a production board to alter this (unless you want to edit serialized values directly in the database).

Currently, in order to edit a hook to change something like which template it hooks into, you have to turn on IN_DEV mode. This is bad because it puts the whole site into developers mode. We should be able to edit a hook's properties without having to enable IN_DEV.