1. Discussion

    1. Support Topics

      Get support for technical issues and using the application.

      185
      items
  1. Documentation

    A look at the different configuration settings available for collaborations.

    Tutorials

    1 post

    How to accomplish useful non-trivial things with the application.

Activity Feed

  1. Last week
  2. Rider

    Uncaught Exception with ips 4.4

    Hello, We had a configuration problem with backends that did not use the same sub-version of php. Regards
  3. Kevin Carwile

    "IPS\Content\ReportCenter" Error

    C:\xampp\htdocs\forum\applications\collab\sources\Collab\Collab.php on line 22 Comment out that line of code.
  4. Guest

    "IPS\Content\ReportCenter" Error

    Thanks @Kevin Carwile, And,How to fix the error to access the forum or ACP again?
  5. Kevin Carwile

    "IPS\Content\ReportCenter" Error

    Group Collaboration 1.4.5 added support for IPS 4.3
  6. Earlier
  7. I have this error Fatal error: Interface 'IPS\Content\ReportCenter' not found in C:\xampp\htdocs\forum\applications\collab\sources\Collab\Collab.php on line 22 installing DEMO version in localhost- IPB 4.3 Groups Collabortation 1.4.4 Now I can´t access to forum or ACP.
  8. Kevin Carwile

    Uncaught Exception with ips 4.4

    What was the problem?
  9. Kevin Carwile

    Sorting collaborative groups does not work properly

    Sorry. That sorting will not work due to technical limitations. The problem is that the sorting happens on the database query level, however, those numbers are aggregated over multiple content sources and database queries inside the collab.
  10. Hello @Kevin Carwile I noticed a sorting problem with the option to do this for collaborative groups whether they are listed in a category or not. The sorting does not respect the option chosen in the sort order. If I have a sort by last answer for example, I see that the sorting of GCs is not done according to this criterion. Example : https://motards.net/gc/c2-associations/?sortby=posts&sortby=last_real_post&sortdirection=desc https://motards.net/gc/c2-associations/?sortby=posts&sortby=title&sortdirection=asc The same goes for sorting by each of the other criteria Can you please tell me if you are replicating the problem on your side and how to correct it ? Thank you.
  11. Rider

    Uncaught Exception with ips 4.4

    Hello, We have found the source of this problem, so I am cancelling this request. Please lock this currently resolved topic
  12. Hi, Since we have ips 4.4 (or 4.4.1) several times a day we have errors : (I don't understand exactly where the problem is but do not hesitate to ask me for more informations about my config (Redis cache system for example)) Thu, 07 Mar 2019 01:44:03 +0000 ParseError: syntax error, unexpected '?', expecting variable (T_VARIABLE) (0) #0 [internal function]: IPS\IPS::autoloader('IPS\\Request') #1 /ips/system/Dispatcher/Front.php(394): spl_autoload_call('IPS\\Request') #2 /ips/system/Dispatcher/Front.php(38): IPS\Dispatcher\_Front->checkCached() #3 /ips/init.php(588) : eval()'d code(87): IPS\Dispatcher\_Front->init() #4 /ips/system/Dispatcher/Dispatcher.php(109): IPS\Dispatcher\collab_hook_ipsDispatcherFront->init() #5 /ips/index.php(13): IPS\_Dispatcher::i() #6 {main} #0 /ips/init.php(665): IPS\_Log::log('ParseError: syn...', 'uncaught_except...') #1 [internal function]: IPS\IPS::exceptionHandler(Object(ParseError)) #2 {main} ------------- Thu, 07 Mar 2019 01:44:03 +0000 ParseError: syntax error, unexpected '?', expecting variable (T_VARIABLE) (0) #0 [internal function]: IPS\IPS::autoloader('IPS\\Request') #1 /ips/system/Dispatcher/Front.php(394): spl_autoload_call('IPS\\Request') #2 /ips/system/Dispatcher/Front.php(38): IPS\Dispatcher\_Front->checkCached() #3 /ips/init.php(588) : eval()'d code(87): IPS\Dispatcher\_Front->init() #4 /ips/system/Dispatcher/Dispatcher.php(109): IPS\Dispatcher\collab_hook_ipsDispatcherFront->init() #5 /ips/index.php(13): IPS\_Dispatcher::i() #6 {main} #0 /ips/init.php(665): IPS\_Log::log('ParseError: syn...', 'uncaught_except...') #1 [internal function]: IPS\IPS::exceptionHandler(Object(ParseError)) #2 {main} ------------- Thu, 07 Mar 2019 01:44:03 +0000 ParseError: syntax error, unexpected '?', expecting variable (T_VARIABLE) (0) #0 [internal function]: IPS\IPS::autoloader('IPS\\Request') #1 /ips/system/Dispatcher/Front.php(394): spl_autoload_call('IPS\\Request') #2 /ips/system/Dispatcher/Front.php(38): IPS\Dispatcher\_Front->checkCached() #3 /ips/init.php(588) : eval()'d code(87): IPS\Dispatcher\_Front->init() #4 /ips/system/Dispatcher/Dispatcher.php(109): IPS\Dispatcher\collab_hook_ipsDispatcherFront->init() #5 /ips/index.php(13): IPS\_Dispatcher::i() #6 {main} #0 /ips/init.php(665): IPS\_Log::log('ParseError: syn...', 'uncaught_except...') #1 [internal function]: IPS\IPS::exceptionHandler(Object(ParseError)) #2 {main} ------------- Thu, 07 Mar 2019 01:44:03 +0000 ParseError: syntax error, unexpected '?', expecting variable (T_VARIABLE) (0) #0 [internal function]: IPS\IPS::autoloader('IPS\\Request') #1 /ips/system/Dispatcher/Front.php(394): spl_autoload_call('IPS\\Request') #2 /ips/system/Dispatcher/Front.php(38): IPS\Dispatcher\_Front->checkCached() #3 /ips/init.php(588) : eval()'d code(87): IPS\Dispatcher\_Front->init() #4 /ips/system/Dispatcher/Dispatcher.php(109): IPS\Dispatcher\collab_hook_ipsDispatcherFront->init() #5 /ips/index.php(13): IPS\_Dispatcher::i() #6 {main} #0 /ips/init.php(665): IPS\_Log::log('ParseError: syn...', 'uncaught_except...') #1 [internal function]: IPS\IPS::exceptionHandler(Object(ParseError)) #2 {main} ------------- Thu, 07 Mar 2019 01:44:03 +0000 ParseError: syntax error, unexpected '?', expecting variable (T_VARIABLE) (0) #0 [internal function]: IPS\IPS::autoloader('IPS\\Request') #1 /ips/system/Dispatcher/Front.php(394): spl_autoload_call('IPS\\Request') #2 /ips/system/Dispatcher/Front.php(38): IPS\Dispatcher\_Front->checkCached() #3 /ips/init.php(588) : eval()'d code(87): IPS\Dispatcher\_Front->init() #4 /ips/system/Dispatcher/Dispatcher.php(109): IPS\Dispatcher\collab_hook_ipsDispatcherFront->init() #5 /ips/index.php(13): IPS\_Dispatcher::i() #6 {main} #0 /ips/init.php(665): IPS\_Log::log('ParseError: syn...', 'uncaught_except...') #1 [internal function]: IPS\IPS::exceptionHandler(Object(ParseError)) #2 {main} ------------- Thu, 07 Mar 2019 01:44:04 +0000 ParseError: syntax error, unexpected '?', expecting variable (T_VARIABLE) (0) #0 [internal function]: IPS\IPS::autoloader('IPS\\Request') #1 /ips/system/Dispatcher/Front.php(394): spl_autoload_call('IPS\\Request') #2 /ips/system/Dispatcher/Front.php(38): IPS\Dispatcher\_Front->checkCached() #3 /ips/init.php(588) : eval()'d code(87): IPS\Dispatcher\_Front->init() #4 /ips/system/Dispatcher/Dispatcher.php(109): IPS\Dispatcher\collab_hook_ipsDispatcherFront->init() #5 /ips/index.php(13): IPS\_Dispatcher::i() #6 {main} #0 /ips/init.php(665): IPS\_Log::log('ParseError: syn...', 'uncaught_except...') #1 [internal function]: IPS\IPS::exceptionHandler(Object(ParseError)) #2 {main} ------------- Thu, 07 Mar 2019 01:44:04 +0000 ParseError: syntax error, unexpected '?', expecting variable (T_VARIABLE) (0) #0 [internal function]: IPS\IPS::autoloader('IPS\\Request') #1 /ips/system/Dispatcher/Front.php(394): spl_autoload_call('IPS\\Request') #2 /ips/system/Dispatcher/Front.php(38): IPS\Dispatcher\_Front->checkCached() #3 /ips/init.php(588) : eval()'d code(87): IPS\Dispatcher\_Front->init() #4 /ips/system/Dispatcher/Dispatcher.php(109): IPS\Dispatcher\collab_hook_ipsDispatcherFront->init() #5 /ips/index.php(13): IPS\_Dispatcher::i() #6 {main} #0 /ips/init.php(665): IPS\_Log::log('ParseError: syn...', 'uncaught_except...') #1 [internal function]: IPS\IPS::exceptionHandler(Object(ParseError)) #2 {main} ------------- Thu, 07 Mar 2019 01:44:04 +0000 ParseError: syntax error, unexpected '?', expecting variable (T_VARIABLE) (0) #0 [internal function]: IPS\IPS::autoloader('IPS\\Request') #1 /ips/system/Dispatcher/Front.php(394): spl_autoload_call('IPS\\Request') #2 /ips/system/Dispatcher/Front.php(38): IPS\Dispatcher\_Front->checkCached() #3 /ips/init.php(588) : eval()'d code(87): IPS\Dispatcher\_Front->init() #4 /ips/system/Dispatcher/Dispatcher.php(109): IPS\Dispatcher\collab_hook_ipsDispatcherFront->init() #5 /ips/index.php(13): IPS\_Dispatcher::i() #6 {main} #0 /ips/init.php(665): IPS\_Log::log('ParseError: syn...', 'uncaught_except...') #1 [internal function]: IPS\IPS::exceptionHandler(Object(ParseError)) #2 {main}
  13. Hello @Kevin Carwile This bug has been fixed by the patch you published following this Group Collaboration problem Thank you Solved
  14. Thank you very much for this patch that actually fixes this problem. in addition, it also fixed the other problem of Activity Feed Displays (The Feed Of All The Site Projects Instead Of My Project Feed) that I reported to you in this topic So all is ok for the moment It's noted for the IPS bug Thank's SOLVED
  15. And i got no money for renewal making me sad.
  16. Thanks, now works well for me! ^^
  17. The collab search was never tested against an elastic search implementation. I was able to confirm that the problem does occur with an ElasticSearch index and not a MySQL index. I published a new version of GC with support for the ElasticSearch index which should solve this problem. However, in the process of troubleshooting this issue and adding support to GC, I noticed a bug in core IPS which causes the permissions to be saved incorrectly to the ElasticSearch index when you edit the permissions of a node. This means that after rebuilding your index, the permissions issue should be fixed, but if you update the permissions for a node, it can then be incorrectly omitted from searches/activity feeds. This is the opposite problem of it being incorrectly exposed, but nevertheless, a problem. You can report that particular bug to IPS support. The bug is located at: ./system/Content/Search/Elastic/Index.php : line 623 The permissions should not be saved to the index as a json encoded string, but rather saved directly as an array for proper searchability.
  18. Hello @Kevin Carwile Thank you for your quick feedback. The steps described are exactly the right thing to do, you have understood the situation. Can you please try to do the same thing again by activating Elasticsearch instead of MySQL for the search and see if you get the same result ? Regards.
  19. liquidfractal

    IPS 4.4 compatibility?

    Awesome...thanks!
  20. Kevin Carwile

    IPS 4.4 compatibility?

    Yes, as far as I know, they are now compatible without issue.
  21. I cannot confirm this. I created a collab. I created a forum inside that collab I set the forum permissions so that non-collab members are not permitted to see the forum or read the topics I posted in that forum. I logged into the site as a different user who is not joined to the collab. I viewed the user profile who I posted with in step 4. I could not see the post in the user activity tab. I could not see the post in the site activity feed either. I logged back in as the original user who is part of the collab and changed the forum permissions to allow non collab members to be able to see the forum and read the topics. I logged back in as the user in step 5. I was now able to see the post in the user activity feed as well as the site feed. I need you to be very specific as to your collab configuration. How is it that you've configured the topics in question to be "totally private and not accessible to guests".
  22. Kevin Carwile

    change in IPS controller leading to error on category?

    Confirmed. I will release a fix for this shortly.
  23. liquidfractal

    IPS 4.4 compatibility?

    Can I just ask if Collabs (as well as other apps you've made) are or will soon be made compatible with 4.4?
  24. Hello @Kevin Carwile I just noticed that on a private Group Collaboration in where topics are totally private and not accessible to guests, it's enough for the guest to go through the profile of a forum member to be able to access all topics from his news feed even if these topics are private! Indeed, if a guest click on the username of a forum member, he can read the content of topics from a sub-forum where he do not have access to... Here are the steps to reproduce this problem : I am connecting to the site as a user I access to a private Group Collaboration whose content is totally private and not available to guests only for Group Collaboration members. I am not a member of the private Group Collaboration. I can't read or see anything from this private Group Collaboration. I click on the avatar of Group Collaboration member, and I access its news feed. I can see the content of private topics that I do not normally have access to on the Group Collaboration because I am not a member of the group. If I click on the topic, only then I get the message "The club content is only visible to members". I can get the same result from the "All activity" feed on the site. It seems to me to be a serious permissions bug at the Group Collaboration that needs to be fixed. Can you please tell me how to fix it or if it is a technical bug to fix it quickly. Thank you for your advice
  25. Hi @Kevin Carwile I updated my forum today to 4.4 and I renewed the App in Marketplace. I updated to the 1.4.6 and I have the bug When I navigate in the Categories, now the text looks in the right side (example): With default theme it's the same And when I clic "Browse" button, the bug appears with error page (screenshot): Sorry for my poor English
  26. Kevin Carwile

    change in IPS controller leading to error on category?

    Uploading a new version to IPS marketplace now with compatibility updates for IPS 4.4
  27. HI Kevin, We're running into this too, and it's holding us back from being able to upgrade to 4.4. Any chance of looking into this sooner rather than later? We do pay our support fees regularly....
  1. View Full Stream