Jump to content

Leaderboard

  1. Wolfie

    Wolfie

    Clients


    • Points

      6

    • Posts

      14,396


  2. Ryan Ashbrook

    Ryan Ashbrook

    Invision Community Team


    • Points

      5

    • Posts

      12,399


  3. Mark

    Mark

    Clients


    • Points

      4

    • Posts

      36,207


  4. Dylan Riggs

    Dylan Riggs

    Members


    • Points

      3

    • Posts

      1,957


Popular Content

Showing content with the highest reputation on 04/04/2013 in all areas

  1. I want to make it so in 4.0 you can drag and drop straight into the editor and it'll put the image where you drop it. I've not looked into how feasible that is though.
    3 points
  2. Just letting you guys know I will be able to update everything in May! That's 3 weeks from now! I will be able to start development again around May 1st. I will then update my themes as fast as possible! Thank you for having been so patient last few weeks! I really appreciate it! Sincerely Sarah
    2 points
  3. I can answer this since I'm experienced with WP -- What you're asking for, this can do. I'll compare them for you really quick In WP -- You have widgets and widget positions. In IP.Content/IPB -- You have ipsLayout For both of these, this is where blocks and all that can go, what Marcher did is pull all of those layouts in IPS and are selectable for use, furthermore (not 100% on this) you can add your own if you know HTML/CSS. Which is also known as adding more layouts to WP. All you do is create a page using the new Visual Layout editor, select the layout(s) you want to use and drag/drop IP.Content blocks where you want, save the page and you're good to go. " alt="vlgmHgr.png"> ^^^^ Layouts VVVVVV Blocks with my current layout at my site... something easy peasy " alt="YvvwL94.png"> And Finally, you can also add your own HTML/CSS to further develop the layouts, something that you can't easily do on the WP side of things. However, after you visually edit your page and go back to manually change something, it looks like smashed ass....
    2 points
  4. Makoto

    Revoking warnings

    Say a moderator warns a member for an offense they never committed, or perhaps you got drunk one night and started warning various members of your forum you didn't like for no apparent reason. (This was not a real life example, don't worry.) Or more realistically, a member appeals their ban/warning and you decide to accept their appeal. What do you do? Well, first you probably apologize to the member and scold your bad moderator if the warning held no merit. But then what? You want to revoke the warning and any action that was given to the user with the warning, right? Well, you can remove any posting restrictions or suspensions manually, but you can't really ever officially revoke or "take back" the warning. The best you can do is manually edit the users warning level, or even delete the warning from the database manually if you so wish. The first option still leaves the warning listed on the users account, unless you decide to warn the user again (without increasing their warning points) just to leave a note that the last warning was repealed. This can be confusing to your other staff members.. and even you, if you're as forgetful of an admin as I! The second option is more permanent, but it obviously requires the client to know how to venture into their database and manually delete the warning entry. Well, I've got a simple solution! Allow staff members to repeal warnings and suspensions! The permission for repealing bans can be assigned on a per-group basis. You can have it set where only you (the administrator) can repeal warnings, or you can give it to your moderators if you so wish. Warnings can be repealed through the MCP or through the users warnings page directly. Once a warning is repealed, the points attributed to that warning will "expire" and any actions attributed with that warning will be automatically reversed. The warning will still be viewable by staff members and even the user himself, but it would be "grayed out" and displayed as repealed or revoked, no longer active. The staff member that repeals the warning may also give a reason as to why the offense was revoked if they so wish.
    1 point
  5. I have recently upgraded from IPB 3.1.4 to 3.4.3 and I have to say that experience has been not good. For the past few weeks since I performed this upgrade I have had to devote almost all of my time to fixing bugs and resolving complaints from my members. The vast majority of these issues, for my site at least, have been the mangling of BBCode in IPB. I know there are plenty of concerns about the RTE, but if BBCode worked as it should in the standard editor it would not hurt as much. While researching all of the problems, I have stumbled on some comments that I find concerning. These are comments where IPS downplays our concerns regarding the RTE and the diminishing level of BBCode support by saying that 95% of the IPB users don't even use BBCode. That may be the case, but I could make a good bet that the vast majority of these same users aren't formatting their posts at all. I could even go one step further and say that those who use BBCode are the ones who are generating the majority of the content on the site, not the casual users who probably wont use any formatting at all. It is important for IPS to remember that the forum owners are your customers and not their visitors. If your product does not work for us then regardless of who visits our site, we are going to have to find a solution that does work. Unfortunately for me and my site, it appears that there is a segment of your customer base that you seem to have forgotten. These are support sites like mine, BleepingComputer.com, that have used and continue to extensively use BBCode in their posts. On support sites a common method is to create databases of pre-made BBCode formatted posts called canned speeches. These can be used as necessary when providing support to a member. We have 1000s of these canned posts on my site and there are many more written by our helpers that they use on the various sites they visit. These types of pre-made posts are commonly shared among other support sites to be used by their staff, essentially creating a global canned speech database. By taking away BBCode you are going to essentially make years of work created on a variety of sites useless. Just because BBCode is antiquated, doesn't make it a bad thing. The advantage of BBCode is that it is a standard that almost all forum software vendors currently use some form of. It works well, and is easily saved, pasted into posts, and portable between a variety of different forum software. The fact that it is so portable allows a helper to use the same canned speech at a variety of forums where they may help, whether that forum is running IPB or vBulletin. Now you say there is no difference between using BBCode and using HTML. I agree, if you can learn BBCode, you can learn the basic HTML codes as well. What is not being mentioned is that the HTML that IPS may allow may be different than what another forum software allows. This makes HTML much less portable than BBCode. On the other hand, BBCode is a standard that is widely recognized on almost all forum software. Using [ b ] means bold. It doesn't matter if it's converted to <b> on one site, <strong> on another, or <span style="font-weight: bold"> on another. For us, the user of the BBCode, all we care is that if we use the bold BBCode on any site, it will make that text bold. By switching to pure HTML, you make it much harder for support sites to coexist with other ones and thus ultimately make it harder for the owners and their power users, who generate the most posts, to work with your software. Personally, I think if IPS could do some form of the following it would make those sites that still rely on BBCode to continue to use IPB, while still allowing you to pursue your holy grail of the RTE editor: Fix BBCode. It's horribly broken in 3.4.x. Codeboxes are useless and consistently cause problems if you use them for anything but the most basic things, tags are broken, and mistakes in terminating BBCode are unforgiving and can cause fatal PHP errors.Stop trying to remove BBCode from IPB and maybe instead just separate BBCode, and the standard editor, from the RTE. Don't try to make them interchangeable. If you want to use and edit BBCode, use the standard editor. If you want to use WYSIWYG, then only use the RTE.Add BBCode controls back to the standard editor. Why were those even removed?Add some consistency to spacing. Why is text after a quote right on top of the quote, while there is decent spacing after the codebox? Here is an example of newlines being stripped from BBCode posts for the sake of the RTE. This one little thing has single-handedly made 1000s of posts at my site and other look like unprofessional and sloppy.Stop changing standard BBCodes. I must be missing something, but I just don't understand the reasoning behind changing the img and list tags?Stop trying to auto-convert BBCode to these new formats. Most of the time the autoconversion just does not work or does something unintended. I would rather the BBCode just not parse at all then you try and fix it for us.As a customer I need to know from IPS what your roadmap is regarding these issues so that I can plan accordingly. All we hear is little comments here and there describing your master plan and to be honest it scares the hell out of me. I have been using IPB for over 8 years, just bought a few more licenses, and the last thing I want to do is switch to another forum vendor. With that said, can you please provide us, your clients, some specific information on what you are planning for the near future?
    1 point
  6. Hello, I've uploaded a test forum to my server, and i noticed that on some of the icons not loading. and I need to press CTRL + F5 to reload all the icons. I wonder, why don't you use CSS Sprites to combine all the icons to one file, and then decide what part of the image to display using css. It's way more efficient, than loading each icon separately and It'll be really useful for large boards. More Info on CSS Sprites: http://websitetips.com/articles/css/sprites/
    1 point
  7. We have had attachment support for many, many years. It has not materially changed in that time (other than being able to upload multiple files at once in the 3.x line). For what it's worth, the "add to post" allows you to choose if you want to insert it into a specific spot in the post, or if you want to simply include the file at the end of the post content. Not manually inserting a file (images are not the only thing you can upload, remember) is actually pretty common.
    1 point
  8. Unfortunately I can't send you any new messages. I've created a username and password for you that should have been emailed to your MSN email.
    1 point
  9. -FP

    [IF] IPB Shoutbox

    The problem with the popup shoutbox buttons not working has been reported and Pete is aware of it.
    1 point
  10. Hello! Some news! I checked the 'infos' bug (the one that says "Bad Request" ) and I'm having no problems. I cannot reproduce it, sorry. I'm leaving it as it is, since it is not a critical bug, and will re-write it on a future update. Now, replying to Laxentis about the unlimited spots issue. I tried to edit a group and selected 'unlimited' free places, and saved. Once I edited back, I saw it was unchecked and the limited number was checked instead. Is this what you are experiencing? If so, it is just an HTML bug, the app already knows that it is an unlimited group, so don't worry about selecting it everytime, though I know it might generate a lot of confusion. I will fix it for sure. :) Thanks for your report :)
    1 point
  11. I don't see what's complicated. The last step is optional. You don't have to attach it to your post unless you want to place it somewhere specific in your post. Which, you would have to do even with drag and drop support. It's a two step process. It's only three steps if you need to attach the image somewhere in the middle of your post instead of leaving it at the bottom.
    1 point
  12. I still believe that notice should be dismiss-able.
    1 point
  13. Cabola

    (TB) Group Format

    You can do some tweaks to the 4.1.1 version's XML file and then import it and it'll work without issues (at least none I've noticed so far) on 3.4.3 Open the xml file and find "public function profileModern" Replace the entire function with this: public function profileModern( $tabs=array(), $member=array(), $visitors=array(), $default_tab='status', $default_tab_content='', $friends=array(), $status=array(), $warns=array(), $show_contact='' ) { /* Init vars */ $_formatted = ''; $namesToReplace = array(); /* Load our class and setup prefixes */ require_once( IPS_ROOT_PATH . 'sources/classes/class_tbGroupFormat.php' ); /* Get our main replaces */ $_formatted = TBGroupFormat::makeNameFormatted( $member ); $namesToReplace[ sprintf($this->lang->words['users_photo'], $member['members_display_name']) ] = sprintf($this->lang->words['users_photo'], $_formatted); $namesToReplace[ sprintf( $this->lang->words['rep_description'], $member['members_display_name'], $member['pp_reputation_points']) ] = sprintf( $this->lang->words['rep_description'], $_formatted, $member['pp_reputation_points']); $member['members_display_name'] = $_formatted; $return = parent::profileModern( $tabs, $member, $visitors, $default_tab, $default_tab_content, $friends, $status, $warns, $show_contact ); if ( count($namesToReplace) ) { foreach( $namesToReplace as $replace => $search ) { $return = str_replace( $search, $replace, $return ); } } return $return; } It was missing , $show_contact='' in the function and , $show_contact in the $return string. 2nd thing you need to do is find the following in the tbGfSkinSearch function: $data['last_poster'] = $data['last_poster_id'] ? IPSMember::makeProfileLink( TBGroupFormat::makeNameFormatted( $data, $data['last_poster_name'], $data['last_poster_group'], 'last_poster_id' ), $data['last_poster_id'], $data['seo_last_name'] ) : $this->settings['guest_name_pre'] . $data['last_poster_name'] . $this->settings['guest_name_suf']; and comment it out, by that I mean make it look like this (add too forward slashes in front of it): //$data['last_poster'] = $data['last_poster_id'] ? IPSMember::makeProfileLink( TBGroupFormat::makeNameFormatted( $data, $data['last_poster_name'], $data['last_poster_group'], 'last_poster_id' ), $data['last_poster_id'], $data['seo_last_name'] ) : $this->settings['guest_name_pre'] . $data['last_poster_name'] . $this->settings['guest_name_suf']; And that's all that is to it really to make the current version work on the newest forum version! The 2nd edit is for the "View New Content" to display correctly.
    1 point
  14. If you take a look at this third-party application, and read some of the reviews as well as the support topic, you'll see some people want to use it just for member-type reviews, at least that's what I got from it.
    1 point
  15. Hello! I'm posting this message to let you know that v2.2.1, which introduces some little new features like the popular requested secondary groups check, is ready. I'm currently making some little improvements on both the admin and front side to smoothen user experience, as well as already making things ready for v 2.3 :whistle: I'll let you know! :smile:
    1 point
  16. Unfortunately our experience has been very similar and we wholeheartedly share Grinler's concerns. Like BleepingComputer we are a technical support community mostly to provide assistance with malware removal and our products. We switched from a highly customized .NET based solution to IPB around the time 3.1 was released. Our main reason was that the software itself was commonly used by other similar communities as ours (GeeksToGo, Malwarebytes, Neowin, BleepingComputer, SpywareInfo, WhatTheTech etc.) and because it was easy to use for our customers. Version 3.1.4 was pretty much perfect for both our and our users' needs but unfortunately it went straight downhill from there. Usability went down the drain when 3.2 removed the option to disable quick replies and introduced the new editor. Like many technical support communities we are working with log files a lot. These can get huge so we usually ask user's to attach them. There is no obvious way to do that using the quick reply. The attachment options are hidden behind the "More Reply Options" button. In 3.1 that wasn't a big deal. Just disable the quick reply function and be done with it. But this is no longer possible now. As a result the most commonly asked question we get and the most common problem our forum users face is how to attach a log to a reply. Something as simple as attaching a file or uploading an image really shouldn't be as much hassle as it is right now. Grinler already explained all the BBCode issues that the switch to CKEditor introduced. They aren't any different for us. Our staff as well as our volunteers had to rewrite their canned speeches multiple times over the past releases since 3.2. Now with 3.4 they even have to maintain different sets of canned speeches: One for IPB and one for literally everything else, as IPB introduced incompatible changes to elemental BBCode constructs like lists ([*] [/*]anyone?). While our employees don't mind, they are getting paid for doing this kind of work anyways, our volunteers do. Volunteers are the life blood of pretty much every support community (this one included I might add). You don't want to make their lives harder than they need to be by regularly breaking something as elemental as BBCode. The new editor has been introduced over 2 years ago. It is still a horrible mess as can be seen by everyone by just looking at the sheer amount of editor related bug reports. And although hundreds of bugs are being fixed with each new version, dozens of new ones show up every time. The fact that you now started to deliberately break BBCode just to get one more bug report closed for the editor is just a testament of how sad the entire editor situation has become. We talked to quite a few other communities what they are planning to do if IPB continues to become less and less suitable for online support and so far the answer has been either to stay at version 3.1.4 or switch to a different software entirely. Both answers aren't in Invision's interest. So we sincerely hope IPB 4.0 will be a step into the right direction.
    1 point
  17. Adriano Faria

    Friends Online

    What's New in Version 1.3.1: Link to PM now opens the pm ajax form (popup), not the full form anymore.
    1 point
  18. Google has also said they use site speed as a factor in determining Search Engine Result Placement (SERP). "Novices may get confused", really doesn't cut it any more. IPS needs to get serious about improving site speed, reducing page size.
    1 point
×
×
  • Create New...