Jump to content

Leaderboard

  1. IPS News

    IPS News

    Invision Community Team



  2. Adriano Faria

    Adriano Faria

    Clients



  3. Charles

    Charles

    Management



  4. Lindy

    Lindy

    Management



Popular Content

Showing content with the highest reputation since 02/24/2009 in Posts

  1. In our spirit of keeping everyone up to date, this topic will serve as a running list of what's new in IP.Board 3.2.0. As we make changes we will update this topic so check back now and then. This is not yet a complete list as we are still making changes, adding new features, and doing other work. If you don't see what you're looking for here just yet please check back later! As always with IPS, everything listed here is not part of a "possible" roadmap. We will only post items on this list when they are 100% complete and included in IP.Board 3.2.0 so you can trust that what we post in public is what you will get. Calendar Improvements SEO Improvements: Consistency: RSVP: Simplification and interface changes: iCalendar support: Moderator Functions Report Center improvements: Editing Member improvements: Moderator Control Panel: New Text Editor New editor and auto-save: Cleaner interface, quick reply, quick quoting: New post alert while typing reply: AdminCP New style: New "like" reputation mode: Easy member management: Improved restrictions: Forum Management: Remote skin editing: Core Functionality View new content and topic marking improvements: and part 2: New Photo Editor: Shared media: Tagging and prefixes: Notification enhancements: and New mobile skin: Miscellaneous Changes "Delete All" button has been added to the SQL error logs page Linear+ and Outline modes removed for topic viewing (they're a hold-over from an older time on the web and it's time to retire them) Support for IPv6 You can now use the member management tools to search for incomplete members Pagination added to the incomplete members page of the ACP If only one skin or language is choosable, the dropdown selector at the bottom of the page will be hidden Member photos and member avatars are being merged into one function: member photo. There was too much overlap between the two features. IP.Calendar and IP.Chat will no longer be bundled in the IP.Board download zip to reduce the size of the download. This also allows clients who have no interest in IP.Chat or IP.Calendar to choose not to download or install those applications. Of course those who do wish to use those applications can easily download from the client area and install them. Rebuild FURL cache button has been moved to the cache management page. It is now possible to rename the “hooks” folder to something else editing the constant IPS_HOOKS_PATH in initdata.php. You can now edit each group’s report center permissions directly from the group management area Report center now supports item marking to remember and indicate which reports you’ve viewed Customers who have purchased Copyright Removal no longer need to enter a separate Copyright Removal key. The copyright will automatically be removed when activating your license. New settings for attachments to limit size of files stored on disk Separate ACP restriction options have been added for managing spam users and incomplete users (access to these areas were previously controlled by the option “can manage banned users”). “Show X Last visitors in profile” now shows always the last 5 visitors if the setting is enabled rather than having a 3, 5, 10 dropdown choice. New ACP tool to create the cronjobs to rebuild sphinx indexes When adding a ban filter in the ACP you will now have an option to enter a reason visible to all admins (the reason won’t show in the public side). Pinned, polls, and moved topic prefixes have been moved to language files (they were previously in the settings area) Many redundant or pointless settings removed. Other settings moved to more logical locations. Some settings groups merged to create fewer groups to go through when setting up your community. System Settings menu item moved to a top-level menu item under System tab so it's available with one-click anywhere in AdminCP. The note box in your My Settings (UserCP) area has been removed. It is a hold-over from years past and doesn't seem to make sense in community software. If you are one of the very few people who use this: make a copy of your notes before upgrade. The unread topic marking system will now remember what page of a topic you left off reading rather than assume you read the entire topic on the first click. Other Important Changes IP.Subscriptions, our simple application to allow you to sell member group promotions on your community, will be updated to work with IP.Board 3.2 but this will be the last update to IP.Subscriptions. IP.Subscriptions has been around for many years - long before communities were assumed to bring in revenue - and it's time to retire it to focus on our more modern application: IP.Nexus. With the release of IP.Board 3.2, IP.Subscriptions will be considered end of life (EOL) and will no longer be supported. Clients should switch to the new IP.Nexus product which is continually updated and contains many more opportunities to monetize your community. A member of our community, Andy Rixon, has agreed to take on continuing development of this product so those of you who use it will still have a solution. The Portal application in IP.Board has existed from the very early days of our company. It was only ever intended as a simple portal and demo of the software but grew a bit over time. It has had minimal updates and the feature set is very minimal when compared to today's expectations of community owners and operators. The Portal application will not ship with IP.Board 3.2 and should be considered EOL. It will be available in the IPS Marketplace after IP.Board 3.2's release for those of you who do use it so you can still upgrade to 3.2. We will also post information on how to easily replicate the Portal's functionality in IP.Content which offers all that the old Portal did and much, much more. A member of our community, Andy Rixon, has agreed to take on continuing development of this product so those of you who use it will still have a solution. As IP.Board 3.2 will have a whole new default skin, the CleanCut skin will become redundant and will therefore no longer be updated by IPS.
    119 points
  2. Performance Improvements Reduced several cache-load queries on the ACP index page Combined two permissions queries loaded on every ACP page into one Added some additional cache-loading calls to other ACP pages (manage applications, manage hooks, manage members) Added some caching for fetching the max version ID in the upgrade_history table, which reduces the number of queries on the ACP manage applications page by the number of applications installed Changed how modules are grabbed when IN_DEV is enabled for menu building (runs one query instead of one query per application) class_forums was getting loaded and initialized twice in the Manage Forums page - fixed so it's not reloaded a second time. Also removed a shortcut for the class in the manage forums file to reduce small amount of overhead/memory. Removed a query for group data on Manage Forums page (group_cache is already loaded, so used that instead) Removed several deprecated functions, reducing the size of some classes and reducing their resulting overhead Edited language export routine (for IN_DEV mode) so that it only exports the data we absolutely need. This reduces the size of our language XML files significantly, and also reduces memory overhead needed to process the language XML files. Index added on ibf_posts.post_parent to speed up certain update queries that previously required a full table scan A lot of unused code in the friend management files has been removed Avatar or profile photo cleanup tools in ACP were unnecessarily loading and instantiating upload class Removed outdated/non-functional coloring in admin logs Calendar has been rewritten, and much unused code has been removed. Caches used by calendar were not being properly loaded at runtime Changed most of the file_exists call in the code with is_file for a faster code execution The bbcode cache now uses the ‘bbcode_tag’ field as array key instead of an incremental integer, that allows a faster data access for single bbcode tags as there is no need to scan the whole array with a foreach. An unnecessary query has been removed from the forum index view (the query used to verify the name used for the friendly URL is correct) Removed unnecessary query from report center report view A cached used by report center was being queried separately instead of at page initiation Report center plugins are now cached for quicker runtime lookup without having to query the database Useless queries removed from report center Some queries that selected all rows and counted them (instead of running COUNT style queries) were changed to be better optimized ACP skin files previously extended the output class unnecessarily. This was removed, resulting in approximately 20KB or more memory savings in each ACP page. Report center plugins are now cached for quicker runtime lookup without having to query the database RSS import now is much faster on boards with lots of feeds setup in the ACP. overWrite header query / method_exists moved from every page load and value is cached in app_cache Developer-Oriented Changes Changes that may impact resource authors and skinners (including removed functions, database changes, new hooks, etc.) $this->DB->force_data_type has been removed. Mod authors should now call $this->DB->setDataType( $column, $type ) instead. $this->DB->no_escape_fields has been hidden. You should use the available $this->DB->preventAddSlashes( array( 'col' => 1 ) ); syntax instead. Login management custom configurations have moved to database handling. conf.php (or conf.dist.php) files are no longer needed (though acp.php still is). search_results, sessions.location, and cache_store.cs_extra are all removed If you have a findIpAddress extension you can now add an array of additional columns to pull from your table as the fourth array member. i.e. "'posts' => array( 'author_id', 'ip_address', 'post_date', array( 'pid' ) )," IPB will now do a better job of cleaning up centralized application data during uninstall, so applications don't have to do it manually. (http://community.invisionpower.com/tracker/issue-25956-attachements-in-support-ticket/) The way hook data to-be-exported is stored has changed. This should have minimal impact on developers as the upgrade routine will update it for developers. This should make working with hooks between multiple developers easier, and make hooks import, export, install and uninstall in a much more consistent manner whether IN_DEV is on or not. Many skin system bugs have been resolved, and improvements implemented, making the skin system more flexible to developers using it outside of normal contexts, while allowing it to be more forgiving of various formatting possibilities (i.e. typehinting for function parameters and spacing around function parameter definitions). Central permission management now correctly can handle more than one permission type within a single application IPv6 is now supported. You should ensure any database columns holding IP addresses are varchar(46) or larger. You should use the new ipsRegistry::getAppClass( $app ); call to load your app_class_(application).php class. This ensures any library hooks execute as appropriate and consolidates duplicative code. You should use the new constants IPS_FILE_PERMISSION / IPS_FOLDER_PERMISSION for file and folder permission values. i.e. instead of chmod( $file, 0777 ); use chmod( $file, IPS_FILE_PERMISSION ); instead. Calendar has been completely rewritten - the DB schema has changed, dates are stored as datetime parts in MySQL, etc. The ACP has a new interface implemented, some of the JS has changed, jQuery is now supported in the ACP Removed 4 data hooks in public_forums_forums_topics: topicViewTopicData, topicViewDisplayData, topicViewForumData, topicViewPostData. All 4 of them can be replaced with a simple skin overloader for the template "skin_topic > topicViewTemplate". Photos and avatars have been merged. Photos thumbs are now cropped at 100px and you can select which area to crop Twitter / Facebook photos are actually imported and re-sized where possible (needs fopen URL wrappers otherwise the thumb URL for the services is used) Some functionality for importing/exporting/rebuilding from and to XML files has been hidden unless IN_DEV mode is enabled Added a second parameter for the function “$this→cache→getCache( $CACHE_KEY, FALSE );” which allows to skip the loading from the database if the cache isn’t loaded already. A new option to define an application when creating an hook, if the application is filled the code checks if it is enabled and if not skips loading the hook file completely. class_forums::fetchTopicFolderIcon() has been changed to return an array of meta-data about the topic that can be used to generate the topic icon, although Rikki is changing how topic icons work in general anyways. pp_*thumb*_x is now pp_*small*_x The sessions API (admin/sources/classes/session/api.php) now supports a different cutoff time rather than the default one, additional joins, ‘where’ query bits, complete ‘where’ query part override. The function “IPSLib::unpackGroup()” now is “IPSMember::unpackGroup()”. ACP group_form.php plugins now support an optional third method: postSave(). This method accepts one parameter (the group ID), is only called if present, is called after the rest of the group data is saved, and should not return anything. Added a getCount() method to the like class to return just the number of followers The setting disable_reportpost has been removed. Our applications now check the report center permissions directly, instead. Hooks Improvements: Applications Improvements: A new extensions file per-app is supported: permissionsSync.php. Class name should be “(app)PermissionsSync” and supports a constructor (ipsRegistry reference passed) and one method with no arguments: updatePermissions(). This method can be used to rebuild application caches when the app permissions have been updated from the central permission manager. Deprecated function getBlogID() in the blog API has been removed, developers will need to use the more updated function fetchBlogIds() makeProfileLink, memberViewImages, makePassword, makeNameFormatted, canReceiveMobileNotifications have been moved to IPSMember unconvertSmilies has been moved to IPSText. The redirect method in the bbcode class has been removed. The “doneScreen” method in the admin output class has been entirely removed. Authors are encouraged to use the global_message/silentRedirectWithMessage() methodology instead. The “redirect” method in the admin output class now simply routes to silentRedirectWithMessage(), and is marked deprecated. The template “global_main_wrapper_no_furniture” has been removed from the admin skin. Function “rebuildSphinxConfig” has been moved from “IPSLib” to “admin_core_applications_applications” classCommunication.php was removed, and classFileManagement.php was extended to handle POST requests (encompassing the only functionality missing compared to classCommunication.php) Almost all private methods have been switched to protected to allow more robust hook capabilities New pagination potions to use a next/previous style pagination. Next/previous style pagination supports AJAX pagination. The column “ban_nocache” has been removed from the “banfilters” table. New adminOutput method setMessage() has been added. Allows to set the global_message, and allows to specify a “sticky” flag or not. ACP Settings are now in their own “settings” module and the templates have been moved as well in “cp_skin_settings”. menu.xml files for ACP modules now support specifying a language key, which can then be placed into “(app)_admin_menulang.php” as “menu__(language_key)” to support menu language abstraction in the ACP. This is optional for apps.
    43 points
  3. We are happy to release the Release Candidate of IPS Community Suite 4.0.0! This means we have left the beta stage where things are unsupported and known to be broken and enter the period between that and final. The Release Candidate phase allows us to partially support the Suite without committing our full resources to it. This step also means that there will still be some bugs in the system but they should not be major issues any longer. You can download IPS Community Suite 4.0.0 RC1 in your client area. IPS Community in the Cloud clients can request upgrades through support. If you are using our Chat product please note that it is not yet available for version 4.0.0 so please do not upgrade if Chat is required. Release Candidate Schedule This is the first Release Candidate and we plan on having several RCs that will be released every few days over the next couple weeks. By doing a rapid release schedule it will allow us to get fixes out to you very quickly and ensure things are as stable as possible for the final, fully supported release. Beta Testers Everyone at IPS greatly appreciates those of you who participated in the beta testing phase. If you did you use beta releases you can upgrade from Beta 8 to RC1 however you may wish to consider a fresh upgrade from 3.4.7 just to ensure you are not carrying over any beta quirks through to RC and final. Important Support Note Release Candidates will be partially supported only. There will be bugs in the Release Candidates. Do not use Release Candidates if any sort of issues will impact your ability to enjoy your site. We will assist you in support with any major problems in installing or upgrading from 3.4.7 to make sure your install is online. However, once the site is online and functional, other less critical bugs may be deferred until the next release to fix those issues. We do plan on a fast update schedule but it does mean you may not get fixes for several days. To reiterate: we will assist with major problems that make your Suite not function (install issues, upgrade issues, major problems) but you may have to wait for update releases for other issues. Please keep these support limitations in mind when choosing to use a Release Candidate. Our Thanks IPS Community Suite 4.0 took at lot longer than we thought it would as we changed the focus of the Suite and were forced to extend our workload and therefore timeline. We are sorry for these delays and we do hope that you see it will be worth it in the end. IPS4 is a great platform and we are very excited to start adding lots of fun features throughout this year. For right now we are only posting this announcement here on our forums so only people like you who closely follow IPS are aware. We will announce to a broader audience as it progresses.
    41 points
  4. Upgrade from IP. 3.4.x to IPS4.0 I am bringing this back again seeing there are still many that want to know how to upgrade. This is an updated version from my original post where the upgrade is explained from start to finish. So you think you are ready to take the plunge and try a test install / upgrade from your current IP Board to the current IPS4.0 beta and later to the final release. Well we will see. {Comment} The following steps are with the assumption you have already created a test install of your current board and made all the preparations leaving your current live board intact. If Not then see the following article. Creating a Duplicate Local Test board from you Live Board. at the bottom of this article. Step One. 1st, Download and run Get Ready For IPS 4.0 1.0.3 to test your current install to see if it is in fact ready. you can get your copy here. http://community.invisionpower.com/files/file/7046-get-ready-for-ips-40/ OK! all is green and good to go then skip the next step and continue on. But you are showing errors that need to be fixed. OK it's not the end of the world so there is no need to find a cliff or skyscraper to jump from. Download and run IPS UTF8 Database Converter 1.1.13 you can get it here. http://community.invisionpower.com/files/file/6823-ips-utf8-database-converter/ Run the converter and let it do its thing, it will take a while. When this is finished re run Get Ready For IPS 4.0 1.0.3 to make sure all previous errors are fixed. If so we can go forward if not now you can find that cliff or skyscraper. NO Just Kidding!!! But you may want contact support with any errors. Step Two. 1st, Make a backup of your Database call it whatever you like as long as you know where to go if the need comes up. 2nd, Here is a trick I use on my local due to a few corrupt downloads that failed causing me to start a test installs from scratch. 1, Create a _347 folder in your root directory and move all your files into it. Another backup you say? Yep! To go along with the above database backup should something go south on you. 2, Providing you have IP.Downloads copy these files back to your Forum Root Directory from the _347folder. Copy the following folders, downloads, public, screenshots and uploads along with your conf_global.php file. Otherwise only public, uploads and conf_ global.php will due. 3, Copy all the files from the IPS4.0 zip file you downloaded from your clients center to your new test install directory. From your browser go to your test install site http://example.com/admin/upgrade/ and begin the upgrade process.......... Go to Site! If the upgrader asks for your license key, add it but remember to use -TESTINSTALL immediately after the license key. 1234567890-12345-123-12345-1234567890-TESTINSTALL Creating a Duplicate Local Test board from you Live Board. Setting up a test board for upgrade is fairly easy but time consuming. In this section of this Tutorial is a guide for those that have never attempted to create a backup test site of the original live site for upgrade compatibility or other testing purposes. For those of you creating a local test server on your own computer using server software like Wamp, Xampp or Mamp. Follow these easy steps. Make a duplicate copy of your forum site by downloading it via FTP Forum Root to a location on your PC. Now log into your cpanel, PhpMyAdmin and Export the compete associated database. In this example we will be using the Wamp environment. Copy your forum site files into your Wamp - www directory example (C:\wamp\www\test-forum) Go into Wamp via your browser PhpMyAdmin, create a new database and Import the newly saved database into it. In your forum directory C:\wamp\www\test-forum find your conf_global.php. In your conf_global.php settings you need to change these settings. $INFO['sql_database'] = 'original'; to $INFO['sql_database'] = 'new_db_name'; and $INFO['board_url'] = 'http://example.com/forum'; to $INFO['board_url'] = 'http://example.com/test-forum'; And the same with the sql user if needed. $INFO['sql_user'] = 'tester'; Now go to the ACP System Settings - General Configuration make all pertinent changes to Path to 'upload' directory and Upload URL. You can find the hint to these new URL's below the text boxes for example: "IP.Board has detected your uploads path as: D:/wamp/www/test-forum/uploads" and IP.Board has detected your uploads url as: These changes will also need to be made in IP.Blog Settings and IP.Gallery if you have them. Go to System - Server Environment - Settings: Server Environment click on Update Settings. This will Sync your new server location settings in your new database. Next go to Look & Feel - Disable or remove all 3rd party skins. Go to Template Tools in the left side panel check all boxes under - Rebuild Master Skin Data click the Rebuild button. When this is finished click Recache Skin Sets after. Go back to System and Cache Management. Click on Rebuild Global Chaches Cache, Rebuild FURL Cache and then Recache ALL. Though some will say this is not necessary but trust me on this. Your IPS 4 upgrade will love you for doing these. Next back under System - Manage Applications & Modules - Disable all 3rd party Apps then click Recache Apps & Modules. Next step Manage Hooks - Disable all 3rd party hooks then click Reimport Application Hooks... Now lastly before doing the actual upgrade go back to your testboard front end via your browser and test to see if all is working correctly. Making sure it is an exact mirror to your live board. ***NOTE*** As you make these changes in the ACP and save each they are also saved in the new Database. (After creating a 3.4.7 test install and all is working....) ​Create a _347 backup folder move all the existing files into it. Thus creating a complete backup of the board you are working with. Do the same with your database by backing it up to another name like "new347-backup". You can do this in PhpMyAdmin. If you have IP.Downloads, you will want to copy (duplicate) the following folders from your _347 backup directory you just made back to your forum root. downloads, public, screenshots, uploads and conf_global.php. If you do not have IP.Downloads than all you need to copy back to the root is your public and uploads folders with the conf_global.php. So if your new forum root directory for the test upgrade is named "my-testboard" or "my-testboard.com" the above files need to be copied there. After this has been completed copy your latest IPS4 beta files you downloaded from the client center to the forum root "my-testboard" or "my-testboard.com" with the other files you just put there. Start the upgrade if it asks for your license key, add it but remember to use -TESTINSTALL immediately after the license key. 1234567890-12345-123-12345-1234567890-TESTINSTALL.
    38 points
  5. Hi, Before I complain, I want to start off with a nice note. Since joining IPB my users have loved the website, commented on how nice it works compared to VB & I have loved your support. When ever I have a bug or problem you guys usually reply pretty fast, sometimes during the night! But here is where I am confused, angry & very, seriously sad. I love IPB. I think it is one of the most solid products in the market, I think it is also the most professional both company wise (how you guys release things when it's ready & not before) and also product wise, it's very professional. For over a year now, I have STRUGGLED to get to grips with pages. I look at the documentation & it's longer than the bible & not very user friendly at all! For over a year now I have messaged support asking how to do things in pages & they say I have to come to the forums as it requires custom code! For simple things like adding the article image in the listing page! For over a year now I have Tried pages, given up... Tried again, given up. There is so much potential in pages - I have seen it on professional website (websites with coders & budget!) but people like me CANT use it. Why.... WHY can't IPB make pages easier. Why can't there be a wizard or Pre made templates! Front page templates... Do you wanna display articles like a blog (photo to the side with description beside), or like a polariod (image with description below), or like a grid. 1 main article & then smaller articles below etc. Joomla asks you things like... Display title, date, time, author. Main article: 0-10, Secondary Articles 0-10. Its so easy! Listing pages... Do you want to display the first image in the article, do you want to display article rating, do you want to display article sorting bar. Article pages... Have a page builder, similar to what you do with blocks. Where you can create fields on a preview page & move them around/edit them. Currently if I want an image uploaded in an article and displayed to the right of the content, I have to custom format it, look up HTML guides on Google etc. I just wish IPB could make pages & frontpage more like Joomla. Joomla frontpage is so easy. Then also keep the difficult custom options for people who are more pro & who know what they are doing. I am so annoyed by the fact I can't easilly create a beautiful looking frontpage & article area, that I am considering going back to another software. Your forum software is so easy to use, but pages is rocket science. Support won't help me, I have seen users here struggle to create things even when working together and helping eachother, and the only other option is to pay someone tons of money... Please consider making pages easier for noobs. PLEASE Danny
    38 points
  6. This is something really boring and extremely repetitive. Every time we install a hook, we have to navigate to Edit Settings, click thousands times until you get the settings for the specific hook. It gets worst if you have several hooks installed. One simple thing would be to add HOOK SETTINGS in Manage Hooks, right here: The idea is to centralize everything in one area, save time! Please consider this! :thumbsup:
    36 points
  7. I spent a couple of hours today building a completely custom homepage with Pages. The homepage made use of a page template, custom wrapper template, two PHP blocks, custom CSS & JS files. As I went along I recorded a few things: Suggestions / Features 1. From a developer stand point, I was immediately stuck in regards to documentation. There's nothing remotely helpful that tells me how to use pages as an advanced user. I suggest a setup guide on creating a custom homepage that integrates with a PHP block. 2. When writing custom blocks, the UX is painful. As a first time user of Pages, there was a lot of trial & error when writing my blocks. Being redirected back to the block index every time I clicked save became tiring very quickly. Ideally, I'd like to write these outside of the ACP like a regular IPS4 plugin. Is this possible? 3. PHP Blocks - At first, I was confused whether this was IPS template syntax or raw PHP. If there were advanced docs, this could be answered pretty easily. 4. When adding templates, (HTML/CSS/JS), the template should be open and ready to edit after the page refreshes. Adding a template, and then having to search through all the folders to edit it is pretty tedious. 5. The CSS/JS include process needs improvement. My JS files needed to be in a certain order yet I was restricted to the incorrect order in which the templates were dumped inside the multi-select menu. In the end, I had to merge the two JS files together to solve that. 6. Global import/export feature. This app is awesome and the potential is huge but as a developer, I have zero interest in building anything for the community due to how messy the setup process is both from a developer & end-user stand point. I could see myself building an awesome homepage package that includes all kinds features. From what I can see, to achieve this at the moment, the user would have to manually create all of this inside their ACP. Manually create the custom blocks, manually add the CSS & JS templates, manually do everything. This complexity needs to be addressed ASAP. Bugs 1. Deleting templates works, but isn't reflected live on the page. It's only gone after a page refresh. 2. Block page badges (custom,plugin etc) have weird alignment. 3. Adding a new page, write some content, switch tab to write the title & page description, go back to the content tab and all the content is gone. 4. "Save and reload" button doesn't work when first adding a page. It just redirects to the index after setting up permissions.
    35 points
  8. Now that IPB3 is here, I think its really time to address the way emoticons are managed because times have changed and boards no longer have just 20 of them, many have accumulated 100's of them. Large, small, light, dark, seasonal etc. Surely there has to be a better, less confusing way of managing them for Admins, and I seem to recall suggestions in the past have been confirmed as having to wait for IPB3 because of its improved programming structure. Sorry I'm going back to basics here, because after several years I still don't understand or have forgotten how Emoticon Management is supposed to work in the AdminCP, and there is still no documentation for it. I don't understand why it is that you can add numerous folders of smilies in addition to the default emotion group, if IPB doesn't automatically include them (the default folder and all additional folders or child folders) when you actually come to post? I also don't understand why you can't turn entire groups of emoticons on and off. One possible solution... Lets say for example you have 150 smilies on your board, consisting of: 50 general ones 50 Halloween theme50 Christmas themed (a little OTT but will do as an example!).It could just as well be large, small, adult, whatever... You wouldn't need to have the 100 seasonal emoticons available to click all year round, and you wouldn't need to have access when posting to the Christmas ones when posting near to or at Halloween, and vice versa. So why not have a folder for each group, and have a check box in the Emoticon Manager to instantly enable or disable each group of smilies as required, and a separate sub-screen to enable, disable or delete individual emoticons within each group, either one at a time or all? This would make things much more manageable for this with lots of smilies, and all smilies would still show in older posts because they are still on the server, just not all in the clickable list all at once. You could take it a step further, by adding tabs (suggested so many times before) to the Show All Emoticon box, so that clicking on default or general would show those, then a tab would be available for the Halloween, large, small etc as defined by the groups in the AdminCP Emoticon Management screen.
    35 points
  9. ? 10 years! ? March 2008 - March 2018 10 years I've been using Invision Community I just wanted to take this opportunity to sincerely thank the whole Invision team. Your software allowed me to build an awesome community, honestly the best in the French poker world: Club Poker. There is also an english version, thanks to IPS Connect. Thank you Invision, for all you've allowed me to do. Your development skills are awesome. While other forum platforms struggle to deliver ugly and cumbersome interfaces, you've managed to develop a top-of-the-art framework. You've delivered a great user interface, fully-featured, and most importantly highly customizable. You've managed to follow the great trends of the always-evolving user experience, along with the new web and mobile technologies. Responsive design, ajax, emojis, oembeds, rich text editor, notifications, external login handlers, image uploads, members mentions, reactions, spam defense, REST APIs… Over the years, you've never rested on your laurels, and this is your strength. Our ability to develop our own applications, hooks, themes, plug-ins, is unbeatable. The Invision Suite offers hundreds of features, but we always have the possibility to extend them, or even to remove them. The power of your platform resides in its flexibility. Of course, many areas can still be improved, but with your framework, we are always able to tune things as we want them to be. Yes, it requires to be a developer to be able to achieve great modifications, but the framework is so full of features out-of-the-box that it surpasses other frameworks, and Invision has become my primary choice to start new projects. I'm looking forward to launch new projects with the Invision Suite, and on the contrary to other frameworks, I feel very excited to use your platform. I can't end this post without stressing out one of the best things at Invision: your support. Everybody at your team is so prompt to answer, and this is really reassuring to know that we can count on your team when developing a project. Keep up the good work! See you in another 10 years
    34 points
  10. There's plenty of room for improvement in IP.Boards searching function. All in all, it's always been a pain for me to use. It's almost always easier to simply use a Google search on my site to find what I want. However, this is only because my site is well indexed by Google. Not everyone is so lucky. In this thread, I'm going to go through some of the problems I've had, in no specific order. My memory is fairly sub-par, so I'll likely recall a few other complaints and suggestions over time that I'll add to this list, but this is simply a thread to get a discussion started. A thread to gather feedback and gather comments and further suggestions from the rest of the community. A thread to hopefully drive more attention to improving one of the most basic and most used functionalities of many forums, searching. Relevance Have you ever tried to search for an app in the marketplace using the built in search function here? Let's give an example. Try and search for this app now: It's called "Links Directory," so you'd search for just that, right? Links Directory. Huh. It's not there. The title of the app is clearly "Links Directory," but it's nowhere to be found on the first page. Why? It seems to be simply because the search results are organized purely by the submission date, relevance has no factor here. The actual app is third to last on the search results page. A quick Google makes the page significantly easier to find. directory It comes up as the very first result. http://community.inv...inks-directory/ https://www.google.c...links Searching by thread, not post author One thing I find rather annoying is that I cannot search by a threads author. You can only search by post author. So, say you want to find a thread started by another user. The only way you can go about doing this is searching by the post author. This will include all threads that the user has posted in. There is currently no way to search only by the threads author alone. A simple extra functionality that I'm interested in hearing others opinions on. This could be useful when trying to search for a story a user posted, a guide a user wrote, so on and so forth. Searching by multiple tags Currently you can search for multiple tags at once, but this isn't exactly what I mean. If you search for an image with the tags "blue" and "nature", as an example, it will return all images from the gallery with either the tag "blue" or "nature". Unlike with keywords where you can define to search for "all words" or "any words", you cannot search for posts that contain "all tags" or "any tags." This is a functionality that I would personally find extremely useful in my community, especially in the gallery and downloads system. When you have a massive amount of images or posts in your community to weed through, being restricted to searching by a single tag at a time can be very inefficient. When you have a community that makes intensive use of the tagging system, why should you be restricted to only searching by one tag at a time? Tags can be used to describe many things, especially in images, and this is why many popular image hosting platforms (such as Gelbooru) make use of this basic feature. My suggestion here is simple. Give the option to search for either "all tags" or "any tags," just as you can with keywords. You can't search archived and live posts at the same time . The technicalities of the problem are understandable, and it's more or less considered a "trade-off" for using the archiving system by most. Apparently, with some configuring, you might be able to get Sphinx to search in both tables. This is a functionality issue I've posted about before This also seems to be an issue already acknowledged by developers, but I'm simply posting it here for the sake of including everything I can think of in my list. (Bug) Searching by title and content in archives only searches by content. This is a bug and a problem I've just happened to come across. When searching by "title and content" for archived posts, it only searches by content. It does not search by thread titles. See the following example. I'm searching for posts with the keyword "Konata" that are made by the user "Shu" in my site's Fanfiction forum. This is what is returned when searching by title and content. Only one result. There should be at least several. This baffled and frustrated me for a while, until I happened to figure out the cause. Now, if we go back and search by content only, we'll get the same thing. But, if we go back and search by title only, see for yourself. The most logical conclusion seems to be that the search function refuses to search by both the title and content, even though this is the default option. Try it yourself. Go search for something generic in your forum archives. Search by both title and content, title only, and content only. See some inconsistencies with the results? This is just one of the problems the archiving system brings. It's a good idea, but there are a number of bugs and problems I've seen because of it, to the point I'm considering simply disabling it and unarchiving all posts on my board at this stage. It's still a relatively new feature though, so I can't really complain all that much about it. ) ( Bug report
    31 points
  11. It's pretty funny actually how people get so worked up. If you actually pause and look at 3.2 compared to 3.1 you will see that, while there are new features, most of what you see in 3.2 is the same stuff in 3.1 just presented better. I assume what people are all :frantics: about when comparing to Facebook is the "Like This" button on posts? Well that is just the same old reputation feature as in 3.1 in a "like" mode where instead of the +/- buttons you get a button that says "Like This" which is hardly worthy of dire predictions in my opinion. Also, as it's what the masses expect, it will be used way more than the +/- reputation. It already has on this forum by the very people moaning about all the "oh it's like Facebook" features: Yes, we have added some "social network" sort of features because our clients asked us to it's what the general public expect. However, we are not forcing anything on anyone. If, for some reason, you loathe the idea of people being able to like things, share content, comment on each others profiles, etc. on your community you can certainly shut those features off in the AdminCP.
    30 points
  12. These types of topics can be disconcerting and even misleading. 1. Some of what's claimed to be bugs are simply not liking the way something functions -- like the inability to delete gallery images because it's a global permission (which is being addressed.) Those are valid concerns and may even be high impact for your particular site, but are nonetheless not bugs and certainly no indication of product stability. 2. Some claim to experience *.bug, yet when you look at support history expecting pages of recent support requests, you find barely any. One of the posters here is claiming instability and an epic amount of bugs, but hasn't had a single ticket in 4 months and not a single bug report has been filed ever. So, either one is suffering in silence or is just jumping on the proverbial bandwagon. Regardless, I admittedly get a little edgy when someone attempts to shake customer confidence and is not providing the full picture. 3. Those that experience issue after issue are very typically in a substandard hosting environment - you'll note time and again our cloud clients rarely have issues. Unfortunately, IPS4 has really highlighted imperfect and outdated hosting arrangements for various reasons. IPS4 is going to perform and function better under modern and proper environments with proper setups (innodb instead of myisam, etc.) It's not going to be stable or perform well on bargain basement servers using desktop processors instead of server processors, VPSs with overloaded parents, etc. It's a bit like installing Windows 7 on a Pentium III -- it will technically work, but it's likely going to be an overall poor experience for you. Now, while I completely disagree with the assessment that releases cause more issues than they fix, I don't want to imply there's been absolutely no concern here and we're perfect... we're certainly not. There have unfortunately been several embarrassingly poor releases and I'll definitely own that. We've very recently took strong notice on a higher management level and have been incorporating many, many changes internally to deliver rock solid releases. We've expanded our testing, both internally and externally. Everyone at IPS, from sales to support, are required to conduct a QA review of each release and sign off on the release board. Impacted areas are given even more attention. We have also brought back an internal QA team comprised of clients from the community that are willing to upgrade live sites with beta releases in exchange for one-on-one live support from our developers and technicians. We've also completely overhauled advanced support and development policies and procedures to improve interdepartmental communication and eliminate repeat issues falling through the cracks. Automated testing is also in the process of being incorporated. All of these things have already had a tremendous impact on stability just in the past 2 releases. We of course cannot rewrite history, but I am deeply sorry that we've not done these things sooner. I know it seems like we're forever asking for your patience, but I would again ask that you hang tight. Throughout the speed bumps and niggles along the IPS4 journey, there's one consistency: we're in a constant state of progress. We've recognized where we've gone right, where we've gone wrong and we're forging ahead a smarter, stronger company with a stronger product line. In regards to bugs vs features - this is also a concern we've recently had. Moving forward, virtually every release will have a balance of minor features and fixes. Major releases (i.e.: 4.2) will be a themed release. For example, the next major release will have an engagement theme. We'll focus, across the suite, on things that engage your users and keep them on the site -- such as better media handling, reputation enhancements, etc. So, you should not see many releases that are all bug fixes or just feature additions. This should keep the product stable while still keeping it fresh and progressing. Finally, if you are experiencing issues - it's imperative you let us know. Keeping things to yourself and letting them fester to later surface in a topic like this is not productive for anyone. If you have a concern, the best way to get it addressed is via the client area. I assure you - you're not bothering us and we want to hear from you before it reaches the level of topic frustration. Thank you.
    29 points
  13. It seems that someone has already beaten me to the "Thank you Ryan Ashbrook" topic, so this will just have to be #2. Early in 2014, I decided our forum software was not up to scratch, and started looking for an alternative. It wasn't an easy decision, because I'd spent a lot of money building a custom solution in Drupal only the year before. Unfortunately, it simply wasn't adequate, and I knew I could easily spend a similar amount again upgrading it, and it would still never be at the level of a pre-built package like IPB. So I approached IPB and asked them if they could migrate our data across, and @Ryan Ashbrook was assigned to make the conversion. As migrations go, I doubt they come much more complicated than this. Our forum has been running for 10 years. For the first 8 years, we ran on phpBB. Then we moved over to our custom Drupal solution. Unfortunately, that conversion introduced some errors in the data. Things were missing or not formatted correctly - so this migration to IPB seemed like the opportunity to re-import them from the original phpBB database. But that didn't make Ryan's job easy. It meant we were not only migrating data from two different platforms - phpBB AND Drupal - and the latter was largely custom-built, so there was no existing converter application. We then needed to combine the two databases, and merge the data without creating duplicates. And of course many topics were started in phpBB, then continued under Drupal... I think you get the picture! We knew that this wouldn't be an easy job, but I don't think either Ryan or I had any idea just how hideously complicated this process would be. The months ticked over, and Ryan persevered. Finally, he cracked it, and we went live in December - with a near-perfect data conversion. Ryan, on behalf of my users who'll never know the pain we went through to ensure the survival of their data... thank you very, very much. Your technical skill is only matched by your endurance!
    28 points
  14. I got an extra field in Downloads, for example (this is a model, happens in any app), with option to search: Then I got a file with this field filled: But when I search for something or here, I got nothing: Also tried to search for: here "something here" something here something+ here+ How it should be? Exactly like PROFILE FIELDS on Members search: Those two (yelllow) fields are profile fields, so the user can search for them. That doesn't happen on Extra Fields model. My Extra Field do not appear in the Advanced Search form: No sign of the Extra Field there. What's the point in allow the user to add a bunch of extra fields and do not retrieve records based on them? I would like to request the addition of Extra Fields in the Advanced Search form, when the app uses it. Thank you.
    27 points
  15. Hi all, I have a request that will only take a few minutes of your time, and will give you something in return. We're finally getting around to creating books and guides to help new customers get comfortable on the Invision Community platform. I'm looking for a few positive quotes and 'soundbites' we can use on a few pages around the site, on social media and in these guides. Hopefully you've got nice things to say. @LaCollision gave us a very nice quote a while back. So things like: That sort of thing. If you have a specific use for Invision Community, then we'd love to hear from you. If you are happy to leave a comment, please also leave your name and URL to your site. If the site is safe for work, then we'll link back to it when using any quotes on our site and on social media. We get a fairly health bit of traffic so I'm sure you'll get a good number of click throughs too. If we get 20 useable quotes, I'll post an exclusive picture of Charles and Lindy holding a hotdog from 2008. I did not seek their permission before making this promise. Thanks for reading!
    27 points
  16. It'd be nice if we could input our own value as for how we'd like a reaction to affect reputation, instead of being restricted to -1, 0 and +1. I'd like "Thanks" to give +2 reputation.
    27 points
  17. So I just did an absolutely fresh install of 4.1.19.4 on a site I am preparing for an academic grant application review. For some reason it installed and yet was utterly unusable because no CSS or template styles were loading at all. Timeline panic made me hit the Outage button. Long story short: @Rhett responded in one minute. Problem fixed in 15 minutes. Before I crawl back into my workhole, I just wanted to say: THAT is service.
    27 points
  18. I believe the polls should be generally upgraded but for starters what I need is to be able to close a poll (not being able to vote) without closing the topic.
    27 points
  19. Hi Guys IPB is awesome and far better than any other forum software available in market. IPB team working very hard to implement new feature every month i appreciate their hard work But now in smartphone world everyone is using mobile devices that have apps to access their favorite content. people don't like first open browser, then type url and then type username, password. Mobile friendly websites are no longer a solution. Forums are facing competition from Telegram groups, discord server, Facebook Groups, Whatsapp Group @Charles PLEASE HELP US !!!!! I know it is very difficult to maintain native app. so Now companies use hybrid approach to cut cost for mobile app. It would be great if IPB team develop the in house Progressive Web app for IPB. IPB theme already mobile friendly so every little to do Just need to implement 1. Service- worker for Offline uses 2. Push Notification for Notifications 3. Login and signup screen (that remember the user name and password) Here some Key Benefits Of PWA over Native App IPB4 team already have brilliant javascript developers. I think it would not too difficult for them to do this. I would like to Pay for this feature separately if it will be developed. It would be Milestone for IPB 4 as compared to other forums software. Others IPB members if you are agree please vote this feature as much you can and share your's feed back too and don't Forget to Participate in Above Poll Question Companies Using PWA!! PWA is not just another Buzz word, PWA again transferring the power back to Web Developers which was lost during native mobile app era. I think REST API based apps for IPB not right approach, From developers point of views, it will make mobile apps hard to maintain and compatible with every new version of IPB and updates of hundered of IPB plugins. However PWA just uses Mobile Responsive of Website. Forums Founders spent both Time and money to make his/her community sustainable. sometime new users like the forums but forget url and browser history deleted,at that time website looses one member ? this same things happened with me many times and may be other members share the same experience. For iOS users or Android users there is more chances, new users of clients Forum website click on App icons (Installed by PWA ) again than open browser inside the mobile, remember the website URL and hit the enter. No matter whether PWA support push notifications for particular mobile os or not :) PWA fully supported in Window 10 redstone 4. We can't ignore the billions machine running window 10. Window 10 PWA app would be huge opportunity to keep the website users engage with website. Just imagine clients Forums apps are installed on users PC. Even They don't open browser and enter forum URL, with single push notification you can make users again engage to your website ? More and more adopting the window 10 This is my humble request to IPB team please please develop in house mobile app for IPB others wise our communities websites will loose the competition in mobile app age. THANKS :)
    26 points
  20. SJ77

    Thank you IPS Inc.

    Hi IPS team, I just wanted to take a moment to thank everyone on the team for the wonderful products and services you provide. I spend a lot of time on here. I have posted several things critical of various aspects of the software. I hope that my contributions are perceived as constructive but I realize that it does not always come off as such. Thus, I just wanted to take a moment to focus on gratitude and what's good about IPS (which in all actuality is almost everything). In my humble opinion IPS provides: The best support of any competing product. Hands down, I love the level of support. Mind blowing fast, and willing to go the extra mile to solve problems. The best product of any competing software. So many things about IPB (and the other apps) just work the way they should. notifications, ajax, moderation options. More than I can list. The best support (community) site. The team really does a great job listening and providing feedback. I spend a lot of time here because I am really excited about IPS. It's honestly what I do for fun. I don't run a business, I have a website as a hobby and IPS is making my hobby very rewarding. Just wanted to spend a moment to express my gratitude. Thank you IPS
    26 points
  21. The day IPB becomes like Facebook is the day I switch to different forum software. 3DKiwi
    26 points
  22. CheersnGears

    IPS 4 Stability

    And mostly due to IPS policy.... hear me out. Nearly every update of 4.x breaks a multitude of sites. Updates are often quickly (sometimes as little as 48 hours) followed by an update to an update. IPS has released security updates on Fridays, and most recently on a Friday just before a 3 day weekend when IPS is closed. Anyone who works in in I.T. knows that you NEVER EVER upgrade production until you've tested it out on Dev. Right? Here's where IPS's policy is failing not just them, but all of their customers. If you encounter an issue when upgrading a DEV environment, IPS will do NOTHING. They won't even LOOK at the issue. They expect you to upgrade your production environment... and if something breaks, let your site sit there broken until they get around to fixing it. As a site operator, that is terrible terrible business practice. From a customer service standpoint, that is terrible terrible business practice on the part of IPS. Here is the scenario that just went down: I upgraded my Dev site from 4.1.12 to 4.1.12.1. After the upgrade, I can no longer create blocks. Get error EX1364 I open a ticket with IPS. They reply that because it is a DEV board, they can't help. I ask if they can give me a hint on where to look. They say no, But they've already had to escalate this same error to Tier 2 support for someone else. I offer my Dev board as another data point for investigation, but they decline and the ticket is closed. I open a Bug Report for the EX1364 error IPS says they cannot recreate the issue (It's magical how often that happens) They close the bug report because it is a development installation. I post this post. IPS management comes in here Explains they listen to customers. Repeats the policy in spite of it not being helpful to anyone on either side. Closes the thread because it is critical of their policy. Now, just to be clear. I am not expecting IPS or support to fix my DEV site into working order. It's a Dev site and it is made to be broken. However, if we customers are going to be forced to be beta testers for every release of the software, then IPS needs to actually work with us to resolve the issues that we report either via ticket or by bug tracker. Furthermore, IPS should not be expecting us to beta test in production. Yippie that Andy Millne cannot reproduce the error.... I CAN, and according to Marc Stridgen apparently so can other people who are running in production. Instead of throwing away customer feedback, IPS should be saying something like "Well, we're not going to fix your Dev board, but we'll take a look to see if we can find the root cause.". If the root cause is some server configuration that is outside their control, then let the customer know and move on, but if the root cause is a flaw in the IPS software that should be corrected, then that is an opportunity for further improvement of the software. And no... buying a second license just for development is NOT an acceptable solution. I'm not buying a second license just because you don't have a QA process. Get your QA process right first before you start pushing out updates.
    25 points
  23. Just wondering if there is any chance of this being implemented. I know we knocked this subject about ages ago but still think its important to address in the light of this modernization of the software. Its all about giving members a choice, even a simple one, (do i want non friends to be able to see my profile page). Even the " its good to share everything, privacy sucks" facebook, allows this option.. Any hope at all for this very important feature being built in this time :thumbsup:
    25 points
  24. Just wanted to say thanks to everyone using the beta release of Invision Community 4.2. We have already fixed your major issues and most people are reporting that things are running generally quite well.
    24 points
  25. Before anyone has a complete meltdown: it's optional and a setting.
    24 points
  26. Charles

    Beta 5 soon?

    ​We may do a beta 6 or may not depending on how beta 5 goes. As was pointed out we are down to just over a page of bugs. Once beta 5 is out we will evaluate from there but we do think we are nearly out of the beta stage So what happens then? Obviously after beta stage is over we will being to officially support IPS4 in that you can request technical support with problems, Marketplace categories for IPS4 will be created, and so on. We will also begin doing both regular maintenance updates (4.0.1, 4.0.2, and so on) and feature enhancements. The release systems in IPS4 are very efficient in that the system generates a download with just the files you need to upload. This will allow us to release updates much more frequently as upgrades will be so much easier. You can expect 4.0.1 to follow 4.0.0 release pretty quickly. Obviously once thousands of clients start using the new Suite previously undiscovered issues will show up so we plan on being very aggressive with releasing updates. Once things calm down and the system proves stable we will also start working in feature additions/enhancements. We have a whole list of things our clients have requested that we plan on adding and the IPS4 framework makes that feasible.
    24 points
  27. 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?
    24 points
  28. As I've noted in other topics, we have piles of "fun" ready to go, however, it's important that we pause and focus on overall stability. Many of you were expressing concern and we've listened. We've closed out hundreds of bug reports and further revised our testing and QA process. We'll get back into the swing of new and shiny stuff very soon, but it's important to take a deep breath every now and then and tie up loose ends.
    23 points
  29. Makoto

    Full SSL support

    It's been suggested before to enable full SSL support for the AdminCP, but I'd like to take things a step further with my own suggestion. I would like to have the option to enable SSL everywhere on IP.Board. Not just on login pages, not just the ACP, but give users the option to use SSL globally, similar to the manner sites like Facebook do. Users would be able change this setting through their account settings, giving them the option to enable or disable global SSL this way, but still letting the admin force SSL on login pages. SSL would first need to be enabled and set up by the boards administrator, of course.
    23 points
  30. Pete T

    shoutbox for 4.0

    i can confirm i am working on Shoutbox for 4.0.x its has no ETA as yet.
    23 points
  31. Charles

    When is IPB 4.0 ?

    Sometime this year is the best I can say :)
    23 points
  32. I think this is a very popular feature request and one that we should be able to accommodate in a future update. It's too late for 3.4.0 but I'll keep this in mind for 4.0.
    23 points
  33. FB will be dead in less then 3 years... so see.. we all have opinions... Remember myspace?
    23 points
  34. Hey, we have published the first article of a series about upcoming 4.6 changes. We took the opportunity for some spring cleaning, so we have removed most of the deprecated methods! They were all marked as deprecated for a while, so you should already be aware of these methods, but here’s a full list of the methods and the new approaches to make your life easier, so if you haven’t already, now it’s the best time to review your code and make sure that none of these methods is used. Most of the changes can already be implemented while the 4.5.x lifecycle.
    22 points
  35. I used Sendgrid based on the recommendation of the IPS staff and because support is built into IPS. Unfortunately the price of Sendgrid is 10x that of Amazon's SES simple email service. I just switched over to Amazon SES and am stuck using the SMTP route rather than via the API because there isn't native support via IPS like there is for Sendgrid. I'd like to ask for or vote for IPS adding support for Amazon SES, just like it supports Sendgrid.
    22 points
  36. Calvin39

    Congratulations

    May I please congratulate Invision Power Services on their kindness in helping me with my board, as a registered blind person IPB 4.1 is an absolute godsend to me, nice to work with, and the staff and help are brilliant. You have made the suite that I can now use myself, or its very easy now to get help, and members really want to help. Its nice to still be able to do things myself and 4.1 allows me to do that, for how long I dont know, but for now I can and its a joy at last. Once again congratulations and thank you. Gerry & Calvin (my Guidedog)
    22 points
  37. "Paste as plain text by default" - when we will be able to turn on this option for all existing and future users in ACP?
    22 points
  38. IP.Nexus 1.3.0 Global Changes () Updated to match the new styling in IP.Board 3.2 both on front end and AdminCP Search functions integrated with AdminCP live search Attention icons to display items needing your attention 2Checkout.com gateway added Support for PayPal subscriptions Subscription option for packages so a member can only purchase an item once Better support to remember a member's original member group when you are using IP.Nexus group promotion feature More admin-level notification options of new activity
    22 points
  39. Martin A.

    Member Map

    Member Map View File IPS 4.4 ONLY For IPS 4.3, use version 3.5.7 Member Map is an application that allows your users to put their (Exact or approx) location onto an interactive map. Member Map has a permission model so you can limit which groups can add to the map. As an administrator you have the ability to create custom groups where your community (when allowed) can place other markers in the map, for example if they would like to post the location of an upcoming meet, exhibits, shops, etc. For developers If you are a developer and you store location data in your app that you'd like to show on the map, you can now do so creating a membermap/Mapmarkers extension. Instruction on how to use it is included in the auto-generated file. Submitter Martin A. Submitted 03/18/2010 Category Member Extensions Compatibility 4.4
    21 points
  40. When upgrading my themes to 4.2, I have been intentionally trying to avoid HTML modifications in an attempt to make my themes "upgrade friendly". In some cases, template modifications are necessary - however based on my own experience and customer bug reports, it has become increasingly apparent that there are design issues with the Default IPS theme. Many pages lack the .ipsBox class which should be used to wrap content. Failure to use this class means text is displayed on the body background which is rarely intended. Every theme which uses an image for the background (or even a dark hex colour) will suffer from this. A screenshot of the Rules confirmation screen from a customers website is shown below. This is easily fixed by wrapping the area with: <div class='ipsBox ipsPad'> however I don't feel as though this is something I should be doing myself - firstly because it means my templates will be modified and secondly because all theme designers can benefit from this. If there could be a conscious effort to go through the suite and apply these classes to the appropriate areas, that would be perfect.
    21 points
  41. Wiki-style editing Would like to at least see edits go into moderation, and the admin be able to see the edit log of what that member did, and be able to approve or edit his/her edits before approval for grammar or just to keep some parts and not others. A difference report would be even better, with the edits highlighted. I know it is not a true wiki, but opening it up to live edits even with groups you trust is not good for databases, there needs to be quality control. (I believe you are not even notified?) Thanks!
    21 points
  42. I'd like to suggest the following two functions as integration among the apps, so admins have at least some sort of barebone cross-functionality: PROMOTE: The same promote as in IPB 3, where you cross-promote a post's content from one app to another app (IP.Blogs, IP.Pages, IP.Board). For example: you promote a post in IP.Board to an article in IP.Pages. SWEEP: Where you aggregate and sweep a post's image attachments or file attachments to IP.Gallery or IP.Downloads, respectively. For example: you sweep the image attachments from a post in IP.Board to an album in IP.Gallery.
    21 points
  43. Hello, would like to suggest a feature for UX The idea is to generate profiles photo for members who dont upload a photo (and they are maaaany), it generate simply based on their first and last name with a random background color. There is a nice plugin for wordpress and many other open source projets : http://codepen.io/leecrossley/pen/CBHca https://wordpress.org/plugins/wp-first-letter-avatar/ http://uttesh.com/ngletteravatar/
    21 points
  44. I don't care how thieves wish to rationalize piracy, it's no different than stealing electricity or cable, as I see it. You may see it as a victimless crime as your neighbor is already paying for it, who cares, right? The reality is, there are real costs to deliver IPS4 and they're not small. Infrastructure alone is in the tens of thousands a month and of course, recurring income is what keeps a company afloat. So, one is not just stealing from IPS, they are stealing from other clients -- normal, honest human beings -- that are promoting growth of the company and product. I've had enough of this "courts decide who a pirate is" and stealing for a greater good (contributing to the marketplace) garbage. This isn't an evening hobby project - it puts food on the table for well over a dozen people. I can't afford a Bentley Continental -- boo-hoo, right? Should I just take one? That's different because there's a "tangible" loss? (These are rhetorical questions.) If you can't afford the software, I don't know what to tell you other than to check out a free software option. Taking something you've not paid for because you can't afford it is still theft. Back to the topic at hand. There is no reasonable scenario in which someone could develop on the IPS platform without direct access to the software (and sharing the software/license, even with someone claiming to be a developer, is against the license agreement) so, in essence, the only people this would serve are people who have pirated/nulled the software. Call me crazy, but I'm not going to trust thieves to submit resources to the Marketplace to be installed on paying clients' sites. Now, with that blood boiling rant out of the way, we actually have considered and are still considering a developer license program. The issue is defining developer for the purpose of the program. We're of course not going to give source code and dev licenses away to anyone who can do echo 'hello world'; and it's not feasible to interview applicants. So, it requires some thought. There's also the argument that you need to spend money to make money. As mentioned, if you want to sell software in the Apple app store, you pay $99/yr. So, perhaps a discounted developer-only license may be a potential solution to whatever problem we're trying to solve here. We can discuss this for a little while longer, but please drop the debating the merits of piracy - I can't tolerate it, even a little. Thanks.
    21 points
  45. Incidentally - regarding the first screenshot - something similar has been on our roadmap since last year and should happen this year. A complete your account/profile feature would be awesome.
    21 points
  46. Seriously, I never wrote a feedback for any company before. My positive experience towards Invision Power Inc. have led me to write one at last. I recommend IPS Community Suite to everyone who is willing to build a new community. The combination of IP.Core, IP.Content and IP.Board is so powerful that is offered nowhere either in PHP or ASP.NET based web scripts. Soon after purchasing a vBulletin Forum License I migrated to Invision Power Services. vBulletin could not meet my expectations in neither product or support they offered, though what IPS have offered to me is quite amazing. The Stable Product: Unlike vBulletin you don't need to have run upgrades every week to fix bugs. IPS Community Suite is indeed a stable product. Professional Support (Not just support): Through Customer Support IPS Staff always point me in right direction and was able to understand my issues properly each time. They are Polite, Cooperative and Knowledgeable. Among them I appreciate Rhett Buck the most for his informative and detailed replies to my tickets. It has been a year since I started development on IPS Community Suite and see no reasons to choose any other product... :smile:
    21 points
  47. I think everyone will enjoy the polish that is 4.0. Here's a proper teaser. (Please do not ask for details on this feature beyond what I post here as I won't answer :smile: ... details will come in blog entries.) This is the popup that comes up with you click to follow a content item. Here I clicked to follow a file in the IP.Downloads 4.0 section. Compare that to the existing follow dialog and you will see just how much more user friendly it is. It's brighter, bolder, and easier to read. The options are clear and not hidden behind drop down menus. The toggle to allow others to see that you followed is also very clear and bold The title of what you are about to follow is shown Notice how the first option is disabled because I have not set up my user notification options. The system notices this and gives me an explanation why it won't work and a link to correct it. In doing so it solves the problem of people following something and not understanding why they get no notification and, more importantly, guides the user to the notification options so they can see all the great tools they have to keep up to date. So just a quick example of the polish and thought being put into 4.0 for you :smile:
    21 points
  48. I'd like to suggest an option to unify avatars and user photos. Essentially, what this would do is eliminate user photos altogether, replacing every instance of a user's photo with their avatar. The user would have one picture identity: the avatar, rather than have two identities: the avatar and the user photo.
    21 points
  49. Honestly, I think the banning system is one of the worst things about IPB. Moderators can't ban members and have them moved to a banned group, bans can't be set to expire and move the member back to their original group (although "suspensions" can), there are both bans and "suspensions" which just ends up making things way more confusing than they should be, and there's no obvious indication anywhere at all that a member is "suspended" which can easily lead to confusion about whether someone is banned or not. And the warning system, I think it's useless. It should be able to give bans and restrictions based on warning points, and it should log all warnings in an obvious place. I really think that this whole "just because vB has it doesn't mean IPB should have it" attitude is holding IPB back. Face it, vB does some things a lot better than IPB does, yet there seems to be this resistance to changing some features to be better just because it happens to be like how vB does it.
    21 points
  50. Hi There is a great feature on some large boards, often boards belonging to large companies They allow visitors to post and only at the end require username & email to perform the registration Many visitors would never register first and then post, they directly post with a form, and discover at the end they have to provide username & email to have their post submitted, so they accept to give those informations This is very powerful, and i was hoping to see this on IPS 4, maybe it is available and i didnt see it ? You must have seen this many times on the web, an example here on a french website : http://voyage.linternaute.com/forum/canada-24002/new
    20 points
×
×
  • Create New...