Chito

There's a recipe for progress, right there.

"Hey, Ugg, see this raw mammoth meat we're eating. What if we used that new fire thing and . . . "
"Shut up. If you don't like raw mammoth meat, go and eat grass."

Lockjit, on 02 October 2011 - 07:09 AM, said:

Oh man...This right here ^^^

If there is one thing I hate about IP is their 'upgrade or get left behind attitude'. I requested help to solve a problem with gallery 3. The response I got was basically a quick flick: "Yeah we fixed it, but you're going to have to upgrade to gallery 4 if you want it". Thanks for nothing IP. This bug was causing many comments to show HTML. I hate gallery 4... however I couldn't let the gallery to be filled of html code and my members were complain about seeing it. So I did upgrade... yeah it fixed the problem but I don't like the new gallery and it took sometime before members stopped complaining about the change. I regret upgrading the gallery, I should have just used an image upload extension.

And now this editor upgrade... very disappointed that they have not supplied any means of switching off the new editor to use the old(don't bother saying there is a switch icon, I know about it... I wrote this reply with the new editor switched off. It is hardly functional compared to the old.). Don't get me wrong, I'm not a IP hater (I like the software over many others). But you haven't exactly been impressing me since 3.1 and gallery 3.

PLEASE IP! Listen to your customers and provide alternate options for those not interested in opting-in to upgrades like this. Just because your wish to move in a direction doesn't mean your customers do. You need to involve your customers in the decisions you make. I'm afraid if IP keeps doing this in the future... I will no longer be a customer(but then, it's not like you guys really care if one person leaves... as long as your bank balances look good eh?).

Man I even had to switch it back to write this reply because the editor wasn't showing the IBeam and wouldn't do returns.

And don't say 'you didn't have to upgrade' because IP IS practically forcing you to. They won't provide good support to people running old versions(they simply tell you to upgrade) and if you want your board to stay up-to-date with security... you have to upgrade. I don't care if IP replies to this, all I would like is for this to be least acknowledged from my perspective.

I also HIGHLY recommend enabling a feature that automatically transfers VSE-implemented CSS modifications from any VSE-unique sheet (e.g. ipb_skingen.css) to the normal sheets, so that there is an alternative means to easily and properly continue styling after converting a skin from a VSE version to a non-VSE version, i.e. without having to manually transfer the VSE-implemented modifications over to the normal sheets and/or resort to re-adding CSS property statements to a VSE-unique sheet.

The way I currently see it, is that the VSE could be a great preliminary tool for making quick hex changes across the board to establish the basic color scheme (and I would use it for such at least until the Search and Replace function works as I would like it to). Converting the VSE version to a non-VSE version would then allow for further modifications to be implemented in the normal sheets.

I think this process would be far more streamlined if the VSE-implemented CSS modifications could be automatically transferred to these normal sheets rather than initially restricted to a separate VSE-unique style sheet without the possibility of built-in automatic transfer (as is currently the case), unless the VSE-unique style sheet structure were updated to include all relevant property statements by default.

This thing is glitchy as hell.  I've tried it on Chrome and Firefox on IPB 3.2.1, and most of the major issues haven't disappeared in 3.2.2.  I'm not sure why it's listed as "beta" because it looks more like an "alpha" to me atm, and possibly should not have even been added in yet.

Among the many bugs/issues are the following:
- the color slider doesn't slide properly (e.g. simply attempting to move the circle thing to choose a different color will completely alter the hue)
- the color picker or other tools often get glued to "on" mode, rendering the VSE virtually unusable until re-launched or reloaded
- colors and/or color previews often don't update after selecting a different color
- selecting a particular area using the element style picker often does not show the corresponding CSS attributes
- many, many, many many many areas are missing!!!

I realize probably most if not all of these bugs/issues have been reported, but I'm astounded they haven't been fixed yet.

Web ◕‿◕ Developer, on 15 September 2011 - 01:40 PM, said:

This is honestly new news to me. I don't care if you are the Leonardo da Vinci of web developers and if you're selling to Bill Gates; $10k+ for a superficial dress is an insane rip-off, and the people who spend that much, regardless of how rich they are, obviously aren't using their brains unless you are a rare god among skinners.

Come on, show us some of your godly work then, you Leonardo da Vinci of web developers!

I think the main calendar view could be developed further more to show more data that are already available:

1. On the month view I would find very useful to have a column on the right side showing all upcoming events. At present we have to click on the next month and search for all the possible future events.

2. The mini calendars under the month view - there is no indication of whether there is any event on the particular day or not. It would be easy to have some of the dates highlighted to give immediate information regarding events on that day.

Originally I posted my question here: http://community.inv...-rename-a-link/ but after I saw the actual solution I decided to post in this forum as well...

Quote

Apparently:

Quote

...is the solution.

It works, but I have to admit it's really dumb and complicated.
If I (computer savvy person) couldn't figure it out what about regular people?

This is a step back from the previous version.

Again, why something simple has been changed to something much more complicated?

I hope someone will create a hook to make it like it was before.

In this topic (http://community.inv...rom-topic-view/) one of the staff member wrote:

Quote

If regular members are supposed to be confused by two buttons how about "link" thing, which even I couldn't figure out, so I had to post a question here?

Why is there so much focus to make every feature convenient for "new users" and a total disregard for "older users' who have been faithfully around for years and know their way around a forum and are comfortable with what they have? If a "new user" was on a specific forum for a few hours, I'm pretty sure they would get used to all the buttons and will not get confused afterward. You're making it sound like it's rocket science to get used to having an extra button to read and click. We're not lab monkeys that have a difficult time knowing and understanding the difference between the "Start New Topic" button and the "Reply" button. Give us some credit here. I'm like Heyhoe, I can get used to it, but IMO it was a nice feature to have it where it was. It's just a pain to have to look for its hook and add it again. But what's the point discussing this issue. IPS will have the final say anyway.

I would love to see an option of both standard and custom icons for forums.

Really, this feature has been available as a modification for nearly every forum script on the market since modifications began, yet only one of them (vBulletin, and they added it badly) actually put the thing in the default software.  It wouldn't be too hard to code in, and it'd work quite well if it was as simple as the version DawPi made

Just have it so with each forum you add, you get an option to add the URL of an icon to replace the default posts/new posts one on the forum index, and voila, one easy feature that would enhance a ton of forums and make IPB look so much more modern (a lot of modern, somewhat stylish forums use this, as do large forums like Gaia Online).

Personally I don't see why everyone's 'Barneys Girlfriend'ing so much about it.
IPB will still be FORUMS. It's just that they add better functionality to track your friends content aswell as new content relevant to YOU.

IPB is not a social networking site per say but they are perfectly capable of adding social networking features without becoming a social networking site like Facebook.

The problem you guys also seem to be having is that you can't see why social networking sites like Facebook has become so popular. They encourage members to engage in conversation. If we can get that encouragement over to the forum-system we'll definitely be a hell of a lot better off.

And you can turn off all of these features if you don't like them. Don't buy blogs if you instead think Wordpress is better. Don't buy IP.Content if you think Joomla is better.
People like you guys are the ones who stop development. Deactivate your IP.Board license and go code your own instead.

Invision Power Services, Inc. is pleased to announce the release of IP.Board 3.2.0 and its Applications!

Everyone at IPS is very proud of IP.Board 3.2.0 and the Application updates. We have worked hard to create a quality, modern community platform and the feedback from our clients has been tremendous.

We are releasing the following new software:


IP.Board 3.2.0
Fully featured community platform including forums, members profiles, calendar, status system, integration, and much, much more.


IP.Gallery 4.1.0
Categories and photo albums for your members to share their images and videos on your community.


IP.Nexus 1.3.0
Fully featured commerce system to sell products, membership access, advertising, digital downloads, and more. Includes tools like a support desk to help manage you clients.


IP.Blog 2.4.0
Allow you and your members to post blogs on your community or syndicate externally hosted blogs easily.


IP.Downloads 2.4.0
Complete file management application including file version control, commenting, and forum topic linking.


IP.Content 2.2.0
Content management for your community - run a full web site or a simply community portal. The possibilities are endless.


IP.Chat 1.3.0
Engage your members in real time chat or send them private chats while in the chat room.


IP.Calendar 3.2.0
Event calendar for your community with multiple calendars, public/private events, and iCal support.




What's new in IP.Board 3.2!

In addition to this list there are countless other minor improvements and changes based on client feedback too numerous to mention.


Calendar Improvements

• SEO Improvements: http://community.inv...o-improvements/
  
• Consistency: http://community.inv...ii-consistency/
  
• RSVP: http://community.inv...-part-iii-rsvp/
  
• Simplification and interface changes: http://community.inv...erface-changes/
  
• iCalendar support: http://community.inv...lendar-support/

Moderator Functions

• Report Center improvements: http://community.inv...r-improvements/
  
• Editing Member improvements: http://community.inv...r-improvements/
  
• Moderator Control Panel: http://community.inv...-control-panel/

New Text Editor

• New editor and auto-save: http://community.inv...ew-text-editor/
  
• Cleaner interface, quick reply, quick quoting: http://community.inv...editor-part-ii/
  
• New post alert while typing reply: http://community.inv...ditor-part-iii/

AdminCP

• New style: http://community.inv...-admincp-style/
  
• New "like" reputation mode: http://community.inv...tion-mode-like/
  
• Easy member management: http://community.inv...ber-management/
  
• Improved restrictions: http://community.inv...s-enhancements/
  
• Forum Management: http://community.inv...rum-management/
  
• Remote skin editing: http://community.inv...e-skin-editing/

Core Functionality

• View new content and topic marking improvements: http://community.inv...d-topic-marking and part 2: http://community.inv...t-improvements/
  
• New Photo Editor: http://community.inv...w-photo-editor/
  
• Shared media: http://community.inv...e-shared-media/
  
• Tagging and prefixes: http://community.inv...g-and-prefixes/
  
• Notification enhancements: http://community.inv...n-enhancements/ and http://community.inv...cations-part-2/
  
• New mobile skin: http://community.inv...te-mobile-skin/
  
• Facebook, Twitter, and mobile updates: http://community.inv...mobile-updates/
  
• Visual Skin Editor: http://community.inv...al-skin-editor/

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.

IP.Nexus 1.3.0

• Global Changes http://community.inv...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
• Hosting improvements: http://community.inv...us-130-hosting/
  
• Customers and purchases: http://community.inv...-and-purchases/
  
• Support: http://community.inv...us-130-support/

IP.Gallery 4.1.0
http://community.inv...-41-dev-update/




Other Applications

Other applications have been updated to work with IP.Board 3.2.0, have received cosmetic improvements, and other minor updates to improve functionality. All applications will get larger updates now that IP.Board 3.2.0 has been released. Keep an eye on our news feed for information.

Code-Level Changes

These are changes made at the code-level of our software during this release phase that may interest our power-user clients.


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 cache 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.inv...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: http://community.inv...s-improvements/
  
• Applications Improvements: http://community.inv...s-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.

Mr. Blogger, on 24 July 2011 - 07:48 PM, said:

So because other forum software doesn't have Ajax reply boxes or pictures at the top of topics that means IPS shouldn't as well?  That's hardly a justification for them not including this important feature.  It doesn't matter if you've seen it before - IPS has been the frontrunner on a lot of features.  Where is this known "fact"?  You can certainly have an opinion about anything, but you have no right to suggest that others don't know HTML because they want this feature in the control panel.  You are insulting everyone that replied to this topic and said they would like this feature.  It's not a useless feature and since you claim you can add tabs in 5 seconds, it shouldn't take you 2 hours to remove it.  I think your last "sentence" hit the tail on the head: "When I rather add it from the templates. "  Not everything is about you thankfully.

What you're saying is basically akin to saying you shouldn't be able to add forums in the admin CP because if you know SQL it only takes "5 seconds".

Mr. Blogger, on 24 July 2011 - 07:41 PM, said:

I am well aware of how to add tabs.  That's not the issue and has never been.   I have tabs on my own site.  The issue is that it should be easy and intuitive.  I see you are being your normal obnoxious, immature self throwing personal attacks around so we'll leave it at that.  My only hope is that IPS doesn't look to you to determine what features to include.  This would be a great feature for those less "experienced" than you.

looking at all the bugs in CKE in the 3.2 version of IP Board I have asked myself this question many times... so I will ask IPS now.....

What was wrong with the old editor?

Why the change to something with so many quirks and bugs?

I know this was tested over and over, but it's not just IPS that is having issues with this editor, go check their dev site and you will see hundreds of bugs and issues with it.

Looking for an honest answer as I saw nothing wrong with the old editor personally, but maybe I'm missing something here?

The editor is so critical in using a forum, and needs to be flawless in my opinion in order to keep members active and posting.