Jump to content

Community

Emsi

+Clients
  • Content Count

    25
  • Joined

  • Last visited

About Emsi

  • Rank
    New Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Unfortunately, this no longer works with IPB4. Any chance you are going to update it, Wolfie? We can unfortunately no longer download it. Otherwise, I would probably just port it to IPB4 myself. It's such an elemental and useful feature that most other forum systems provide as part of their standard permissions. It baffles me it still hasn't been made a default permission at this point.
  2. Defaults have changed to enforce a more strict adherence to the SQL specifications. In any case, we moved to MariaDB and the issues disappeared. You may still want to look into the 5.7 issues though and set up a VM. Because it is the default MySQL server shipped by various large server distributions. Ubuntu LTS being one of them.
  3. Tried new version 3.1.8. Attempt to rebuild the cache leads to this: SELECT `tag_aai_lookup`, `tag_meta_app`, `tag_meta_area`, `tag_meta_id`, `tag_id` FROM `core_tags` GROUP BY `tag_meta_id` ORDER BY `tag_id` ASC LIMIT 0,100 IPS\Db\Exception: Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'support.core_tags.tag_aai_lookup' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by (1055) #0 /home/support/public/system/Db/Select.php(346): IPS\_Db->preparedQuery('/*IPS\\advancedt...', Array) #1 /home/support/public/system/Db/Select.php(408): IPS\Db\_Select->runQuery() #2 /home/support/public/applications/advancedtagsprefixes/modules/admin/manage/tools.php(277): IPS\Db\_Select->rewind() #3 [internal function]: IPS\advancedtagsprefixes\modules\admin\manage\_tools->rebuild() #4 /home/support/public/system/Dispatcher/Controller.php(85): call_user_func(Array) #5 /home/support/public/applications/advancedtagsprefixes/modules/admin/manage/tools.php(26): IPS\Dispatcher\_Controller->execute() #6 /home/support/public/system/Dispatcher/Dispatcher.php(129): IPS\advancedtagsprefixes\modules\admin\manage\_tools->execute() #7 /home/support/public/3uskbvr1xqi24czhwy51/index.php(13): IPS\_Dispatcher->run() #8 {main}
  4. 3.1.7 according to the applications list. I just bought and downloaded it from the marketplace yesterday. IPS version is 4.1.17.1.
  5. Any attempt to resync the cache and get proper badges in the topic list results in this error: SELECT DISTINCT `tag_aai_lookup`, `tag_meta_app`, `tag_meta_area`, `tag_meta_id` FROM `core_tags` ORDER BY `tag_id` ASC LIMIT 0,100 IPS\Db\Exception: Expression #1 of ORDER BY clause is not in SELECT list, references column 'support.core_tags.tag_id' which is not in SELECT list; this is incompatible with DISTINCT (3065) #0 /home/support/public/system/Db/Select.php(346): IPS\_Db->preparedQuery('/*IPS\\advancedt...', Array) #1 /home/support/public/system/Db/Select.php(408): IPS\Db\_Select->runQuery() #2 /home/support/public/applications/advancedtagsprefixes/modules/admin/manage/tools.php(276): IPS\Db\_Select->rewind() #3 [internal function]: IPS\advancedtagsprefixes\modules\admin\manage\_tools->rebuild() #4 /home/support/public/system/Dispatcher/Controller.php(85): call_user_func(Array) #5 /home/support/public/applications/advancedtagsprefixes/modules/admin/manage/tools.php(26): IPS\Dispatcher\_Controller->execute() #6 /home/support/public/system/Dispatcher/Dispatcher.php(129): IPS\advancedtagsprefixes\modules\admin\manage\_tools->execute() #7 /home/support/public/3uskbvr1xqi24czhwy51/index.php(13): IPS\_Dispatcher->run() #8 {main} It appears someone reported this exact problem before and it seems to be related to MySQL 5.7 almost a year ago. Is there any way to fix it?
  6. This will still require all our volunteers to maintain multiple versions. One pre-formatted in a Word file or so so it can be copied with formatting in place and then the BBCode version of it for all other communities they participate in. That being said, volunteers are only one part of the issue. Some of the tools we use on a daily basis will emit BBCode formatted logs, that are easy and convenient for the user to post and for our experts to read due to the embedded BBCode formatting. Breaking BBCode will also break these logs. In the best case scenario the BBCode would just be ignored, which may annoy the expert that is helping you clean your system, but is essentially just a nuisance. In the worst case scenario the BBCode breaks the display of the log somehow, leading to malicious entries being missed or entries appearing malicious although they actually aren't. Both can end quite badly for the user. I am glad that you found a way to work around the messed up BBCode parser in your community. But you have the admins of two of the biggest malware removal communities out there telling you BBCode is essential for their type of community. You may want to listen to them.
  7. We are pretty much in the same boat as Lawrence. Every single big IP.Board release that we experienced (3.3, 3.4, 4.0) has been breaking fundamental BBCode constructs for us that all our employees and volunteers use dozens of times every day. What makes things especially frustrating is that in every single case you didn't even have to touch corner cases to break things. Just use two separate lists in the same post in 4.0 and you end up with results that will leave you completely baffled. I can understand that bugs happen, but especially for the LIST tag having to jump through the same hoops on every bigger release is becoming increasingly frustrating, since these are the kinds of bugs you would expect every halfway decent test suite to find.
  8. BBCode has been effectively removed. While it is technically still in there, it it completely and utterly broken. That means neither we nor every other technical support community will be able to upgrade as we do rely on canned speeches a lot that are based on BBCode, exactly as we feared when we brought it up. At least we now know how much Invision's word is worth.
  9. Unfortunately our experience has been very similar and we wholeheartedly share Grinler's concerns. Like BleepingComputer we are a technical support community mostly to provide assistance with malware removal and our products. We switched from a highly customized .NET based solution to IPB around the time 3.1 was released. Our main reason was that the software itself was commonly used by other similar communities as ours (GeeksToGo, Malwarebytes, Neowin, BleepingComputer, SpywareInfo, WhatTheTech etc.) and because it was easy to use for our customers. Version 3.1.4 was pretty much perfect for both our and our users' needs but unfortunately it went straight downhill from there. Usability went down the drain when 3.2 removed the option to disable quick replies and introduced the new editor. Like many technical support communities we are working with log files a lot. These can get huge so we usually ask user's to attach them. There is no obvious way to do that using the quick reply. The attachment options are hidden behind the "More Reply Options" button. In 3.1 that wasn't a big deal. Just disable the quick reply function and be done with it. But this is no longer possible now. As a result the most commonly asked question we get and the most common problem our forum users face is how to attach a log to a reply. Something as simple as attaching a file or uploading an image really shouldn't be as much hassle as it is right now. Grinler already explained all the BBCode issues that the switch to CKEditor introduced. They aren't any different for us. Our staff as well as our volunteers had to rewrite their canned speeches multiple times over the past releases since 3.2. Now with 3.4 they even have to maintain different sets of canned speeches: One for IPB and one for literally everything else, as IPB introduced incompatible changes to elemental BBCode constructs like lists ([*] [/*]anyone?). While our employees don't mind, they are getting paid for doing this kind of work anyways, our volunteers do. Volunteers are the life blood of pretty much every support community (this one included I might add). You don't want to make their lives harder than they need to be by regularly breaking something as elemental as BBCode. The new editor has been introduced over 2 years ago. It is still a horrible mess as can be seen by everyone by just looking at the sheer amount of editor related bug reports. And although hundreds of bugs are being fixed with each new version, dozens of new ones show up every time. The fact that you now started to deliberately break BBCode just to get one more bug report closed for the editor is just a testament of how sad the entire editor situation has become. We talked to quite a few other communities what they are planning to do if IPB continues to become less and less suitable for online support and so far the answer has been either to stay at version 3.1.4 or switch to a different software entirely. Both answers aren't in Invision's interest. So we sincerely hope IPB 4.0 will be a step into the right direction.
  10. Any idea when you will tackle the custom field issues? Those are pretty much the only thing holding us back from actually using Tracker.
×
×
  • Create New...