Jump to content

Wolfie

Clients
  • Posts

    14,485
  • Joined

  • Days Won

    35

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by Wolfie

  1. She mentioned that. :thumbsup:
  2. I'd like that if the following happened as part of it.. Optionally download updates as they become available. Notify me when an update is available and, if set to download, if it's ready to be installed yet. Ability to check which version of a file is already on the board (if I have a newer version than whats in an update, then that file will be skipped) Allow me to choose when it will do an automatic install of updates and what to do during the process... When: Which day(s) of the week, what time(s) of each day, or only notify me when it's ready but wait for me to do the update. Perform automatic check of the database. If any errors are found, abort automatic process and notify me. Backup database and board files (can be set to only backup files that will be affected or all files). Take board offline. Perform the backup. If any errors detected, restore to pre-update status and abort update process (return board to online status). Run check on database. Repair if needed. Optimize. Put board back online. Notify admin of update and include a link to a logfile in a predetermined log folder (.htaccess protected) which would include various details of the update process. [*]Notify me if any of the updated files include any files that I've modified. If I edit one of the primary files to put in a mod, then I'd want to know that a file that will be updated has been modified from the original. [*]If the update is labeled as critical/severe, an option to install anyway, despite other settings. [*]Tell me what the updates will actually do along with any known issues with installing the update (such as, if it's known to upset/break/disrupt any known mods). The part about keeping newer revisions of a file may confuse some so I'll explain. If it's set to wait for an admin to activate an update, but critical updates are automatically installed, then if a critical update includes a file that's newer than a pending update contains, then obviously you want to retain the newer version of the file. This idea might actually be better as an add-on application that's only available to admins with access to certain ACP areas. But such a function/module would certainly slurp in a number of new Admins from other software brands, if this were to be developed and maintained. :)
  3. This reminds me. You can view only topics needing approval and topics with posts needing approval (and only the posts needing approval within a topic). What about the flipside? Being able to view a topic as though you don't have the authority to view/approve hidden posts? Also, Brandon D is working on this project. Not a feature request, but would be nice if people gave it some support (kudos, encouragement, etc): Forms System 1.0.0 It's basically a Form creator for IPB3. Create feedback forms, surveys, applications, support, etc etc etc. He only announced plans for it a few days ago, but I've noticed a few people wanting something like it and not having seen his announcement yet.
  4. Oh yeah... Preview button/feature when editing your signature!!!
  5. Oh you foolish boy, you don't know how wordy I can be. ;) I'll try to keep this short though. ACP/Skin editor, make the left menu panel collapsible (like on the board index, the items on the right). Also, make the template names a fixed width to make it appear neater, but also can be minimized. More ideas to come... Edit: more... Time controls when posting. By this I mean start and stop times to post a new topic/post or have a topic pinned. When telling when to make a post, the start time would be when to post it, the end time would be a "delete" time. Also, if a "bump" feature is included, automatic bumping (once every 24 hours after the topic has been bumped or had a post made to it), with a limit on how long it can be bumped after the last post inside the thread. Say 3 days as a default (for a particular forum), someone makes a topic and someone with bump powers enables autobumping, then for 3 days after the last post in that topic, the topic will get bumped every 24 hours. Edit: Even more... Be able to backtrack where you got +'s and -'s from (on posts). Fixed "read" markers. Also, when a subforum of a subforum has a new post, have the green indicator thing of a bob turn on, so people know where to look. The main forum folder is sometimes lit (new posts) but none of the shown subforums are green, so you don't know if it's giving a false indication or not until you click that forum and then see the sub-subforums and see green indicators (unless it's another level deep, then you have to hunt for it). Be able to have age/gender based criteria. With this, if someone sets their age or gender on the board, then they can choose to have that information hidden but can NOT change information itself. So an "Adults only" forum could be made or some other restriction and someone couldn't change their information to gain access to it. If someone is a global moderator or is assigned as a moderator for a forum, then they are only affected by permission masks (ie, not age nor gender). Be able to assign someone (or a group) as a forum owner. Forum owners as given special permissions as the can recruit people to be moderators of that forum (and only that forum). To keep it simple, the difference between owners and moderators is that owners can promote/demote people for that forum. They cannot create their own forum or subforums, that has to be done by someone with ACP access. (Still more to come!)
  6. In the Lo-Fi skin, the tab for Calendar isn't even available. So I would presume it's not intended to be viewed in LoFi. The fact that it'll load up without showing an error of some sort though should be reported as a bug.
  7. I gave you a + on that one. I've recommended it myself, where on edit, the pre-edited post would be saved so it can be looked at later if needed, with those pre-edits having an optional life expiration. Would be nice to have a wiki-like comparison done, so that it's easy to see what changes were made. I think something like this may be available already, for the sidebar. If not, that's where you'd want it. Since IPB uses a virtual/dynamic cron, the bulk mailer runs based on the amount of user activity on the board. If your board is very active, then just set the number of emails per cycle to like 1. It may still send out more than 20 every 15, but at least would spread it out some. Otherwise, at this point, you'll need a mod. An option to limit the number of emails sent out (as a global setting/restriction for the board) would actually be nice, because then it could be used to prevent an overload, especially on boards that have a high volume of spammers.. Of course, the catch 22 on that is that if the board was trying to prevent spammers, they'd do a better job where it wouldn't be necessary. :lol: But still, would be nice because it could reduce the load on a very busy board. Also, the ability to change the default number emails per cycle for bulk emails. I don't mean per email (you can already change it at that time), I'm talking about the value placed in there. It's 20 now, but what if I want to restrict it to 10. I don't want to have to change it each time.
  8. Introducting Forms System 1.0.0 That, perhaps?
  9. It's still accessible via the forum jump in the bottom right of each page.
  10. Where in the gallery did you find it?
  11. Which gallery? Who is the owner of it?
  12. That's for one week of the month, I'll take her for the other three. :)
  13. http://forums.ahmodding.co.uk/index.php?showforum=8
  14. I'm not finding it... I tried doing a live search for 'spam' and don't see anything that matches, unless I'm just being a dummy..
  15. Another feature to add. Ability to have new registrations compared to collectible data from sites such as stopforumspam.com and how to act based on the information collected. Like if there are under 3 'hits' for the email address, allow the member to join without penalty. Under 7, able to join but are automatically put on a mod-que restriction (with the time of mod-Q being configurable). If they hit above that number (say 7), then they are told that they have failed a security check and need to contact the board administrator in order to be able to join, with a final value where they would just be informed that they will not be given any form of access on the board. This would permit the admin to have levels of restriction based on the number of reports of that email (or IP address) being a spammer. As another thought, perhaps it could be sort of like the rank system, where if the number of reports exceeds, what action to take. If number of [_]email hits exceeds [__] or [_]IP hits exceeds [__], then [_] Require email validation (if not already required) [_] Require admin validation (if not already required) [_] ModQ member for [__] minutes/hours/days/indefinitely [_] Require user to contact admin first [_] Reject user and [_]ban IP address for [__] min/hour/day/indefinitely (0 doesn't ban IP address) I think that helps explain it better. For checking for hits, then XML/API methods could be defined.
  16. Oooh, nice idea. But instead of not letting guests see it, it should be configurable by member group. "Can view the online list page?" So that they could see who's online in the board index, but not use the online page to see others activities. Could be useful for cutting down on the "sneaky" spam, because then a "newly registered" members group could be denied access to it and they wouldn't be able to watch and notice which threads are being read more than others at the current time. I made some requests in a thread called Feature suggestions requests v3.1.x or later Per post/topic, disable someones ability to edit a post they have made or their ability to reply any further to that topic. * Disable edit post - if a mod makes a change, member changes it back, mod can make change again and then 'lock' that post from the member editing it again. * Disable topic reply - if they're stirring up too much trouble in a topic and won't take the hint to relax, then why lock the topic when the topic can remain open but the member not be allowed to post in that topic? Should be "suspend from replying to topic for [__] minutes/hours/days or [_] indefinitely". Perhaps even be able to suspend them from being able to read the topic. (Can see it's there but just can't read it) I mentioned it before and I'll mention it again, just in case it helps to get it into v3.1. In the "top 20 posters" for the current day, making it so that the number of posts (for the last 24 hours) is a clickable link that would do a search for all of that members posts for that time period. Would be helpful when there is someone that has been a problem in the past and you want to see only their most recent activity to make sure that they aren't (advertising, causing flame wars, etc). Search results default sorting method... In ACP, admin should be able to decide between relevance or most recent. Also whether or not to allow members to set their own preference (an admin may have a reason for forcing it to always be one or the other). When a new member joins, their choice should be set to the board's default choice. Also, staff should be able to disable relevance or date sorting.. Let's say that too many people gripe about how their results don't seem to be 'relevant' to their search, then the admin could turn it off and that would default everyone to the date sorting. Or if the admin wants people to come across older topics, perhaps to bring new life to them, then the dates sorting could be disabled. Just basically some additional controls over it. Admin should be able to modify a members sorting choice and also (similar to the skin tools), be able to change the choice for all of the members that are part of a member group. Yeah yeah, a lot of options for just one little thing but it has merit. At the very least, board default method (which would be the default for new members) and ability to force it as board wide or let members choose. In ACP, when viewing/editing ban restrictions, have tabs for IP/Email and Name banning, where the tab being shown would be the default type of ban chosen when going to add new bans. (But could still change it before submitting). When submitting a new ban, then the tab for that ban type should be shown (if they add an email ban while on the IP tab, then take them to the email tab when the page loads). Also be nice to be able to submit multiple bans with one submit, so a multi-add form would be nice. Here's a major request. Be able to decide between wildcard and regular exp​ression format (per entry). I know that the wildcard bans are converted to regular exp​ressions for actual comparisons/matchings, but an admin would have greater power for banning multiple emails/names in one move if they could enter in a regular exp​ression directly. For example, if someone wants to ban a few email sites.. "@[ey]?mail\.(ru|nz|biz)" would cover a wide range of sites that have been known to cause problems. It's an example off the top of my head so please don't jump my case if it covers something it shouldn't or doesn't include something you think it should. :P When you are on someone's profile and click to send them a PM, if you will not be able to complete that PM for some reason (user has their PM turned off for example), notify the user then instead of when they click the "send" button. If they do it from their own messenger, where they have to type in the name, then that's different. Some way of detecting if the board is on an IPS server or not. If not, give the admin the option to not honor a members choice to not receive bulk emails. I don't know if IPS hosting customers can modify their own source but if not, then perhaps include a line to edit in a specific file that would enable the option. If it's not possible, then some option for being able to send out an email to everyone in the selected user groups in an effort to test email addresses. Way I see it, if someone doesn't have a valid email address, I don't want them to have access on the board. Wouldn't have to be a big email and could be something internal that can't be easily altered. Something small like "Account status checking" for the topic and inside a brief explanation letting the member know that no action is necessary, it's just checking for expired accounts and to please not mark it as spam. Also restricting how often it can be used would be a nice idea, to prevent abuse. Facebook: * Be able to prohibit the creation of new accounts using FBC, but allow members to associate accounts with Facebook. * Allow admin access to view/edit a members Facebook information (including a link to view the members profile). Custom profile fields: Include 2 lines that the admin can use, both optional of course. First line would be a URL/link line. Second would be a display format. Both would replace {content} with the members input. This would be useful when external services are made into fields, such as Twitter or Photobucket, etc. Also could be used to replace all the if/then and else-if statements in the skin to cover things like AIM, MSN, etc. Invisible/Hidden forums. If set to invisible, then the member could see use it if they can get to it. Sometimes you just want to hide a forum from view (and from the drop down list) but want to include it some other way. :) Topic/post "Notes" and a true "history". Perhaps more like a "change log". * Notes: staff notes on a topic or a specific post. For a topic, if there have been a couple of problems in that topic then someone could write a note that they've given a warning for things to settle down, before it needs to be locked, so other staff don't have to go digging around to find the warning or to see if one has been made. For a post, if a member got a warning about something they said in a post, then a note could be attached to say "I talked to them about their comments in this post." Also, a button to review any Report Center or Warn Panel activity. * History: If someone makes an edit to a post, have an original of that post saved away pre-edit. This should be done in a separate table, be optional (for obvious reasons) and also have an expiration so the old pre-edits eventually go away. (Should be several options related to this, such as when to expire a pre-edit copy, if the very original pre-edit should remain longer than other pre-edits, per group, etc). IP.SubWay add-on! I'll think of more later... I always do. ;) Oh oh oh.. Per forum, force "Edit by" if a post is edited, even if that member is in a group that lets them remove that line. Exception would be if they also have ACP access. Stalk much? :lol:
  17. Try blowing up the internet by Googling "Google", then after the commotion dies does, use Google to search for RTE problems with Chrome. Also check Chrome support, see if anyone else has an issue.
  18. XP/SP3 here. Does it do the same thing when you switch user accounts on your computer?
  19. Google Chrome is up to date (2.0.172.33) Could be a version issue.
×
×
  • Create New...