Jump to content

Wayne B

Clients
  • Posts

    454
  • Joined

  • Last visited

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Posts posted by Wayne B

  1. You would only need to do it once to select the forum as a destination. The import will work on the forum while it is part of a collaboration or not. In fact, there is no internal difference between a collab forum and a non collab forum. Only GC knows the difference.

    The hook you speak of is already in place. It actually does the reverse of what you said. It filters the forums out that GC knows are part of a collab, because the core system doesnt know the difference. Otherwise management would become very messy with main site forums being buried and sandwiched in groups of collab forums (that could also possibly have the same names making it difficult to know if you even have the correct forum selected).

    Not only that, but the IPS framework uses the same method to list forums in the main site index as it does in the forum select form field, so without the filter in place, all collab forums would also be listed in the main site index as well. And there is no practical way for the hook to know if the forum list is being requested for a form field or for the index page, so you cant have one without the other. In other words, if its exposed to the form select field, its also exposed to the forum index and every other part of IPS core that works with forum lists.

    I think the best solution is to just move the individual forum in question out of the collaboration temporarily to expose it to the select field on a case by case basis rather than exposing every forum in every collab all at the same time.

    Sorry Kevin I didn't realise it would continue to work once moved back, my misunderstanding. As that's the case and with the rationales you have given above I agree with what you are suggesting most definitely.

    At least we are all thinking it through though ?

  2. ​Here's what you could do as an administrator:

    1. Move the forum out of the collaboration temporarily.
    2. Set up the RSS import.
    3. Move the forum back into the collaboration.

    I believe that will accomplish your goal.

    Hi 

    The issue with that is it would be impractical to do as the imports are not a one off. For example some are set to import new content every hour some are set for once a week through the current tool in the core. 

    I think it would be ideal for a more integrated solution or perhaps a hook (if available) that allows you to hook into anywhere in the ACP where the list of forums shows to select adding all available collaborations to the list. 

    This would resolve the RSS issue however it would also integrate collaboration into the many areas of the ACP where the forum select  list is available for selection.

  3. For the benefit of everyone else I have also asked @Kevin Carwile for the following which he has said he is working on in a future release to save others asking the same thing;

     

    Would it be possible to remove on a category by category basis the requirement for Joining a collaboration? Just being able to disable this element would give it more flexibility for our particular needs.

    Also if it is disabled, prevent a collaboration owner having the ability to re-enable it.

    This also brings me on to the ability to control on a category by category basis which parts a collaboration owner has access to. For example if I didn't want in one category a collaboration owner to have access to manage roles or access to manage pages etc making it that collaborations in these categories are required to follow a model for example.

  4. Hi @Kevin Carwile

    I currently use the RSS import tool in the ACP - that allows you to specify which forum it should be imported to and the status etc so unapproved/hidden on import, visible on import, locked etc

    Its great for auto stimulating debate by providing news articles to discuss from whatever source I configure. 

    The issue is that I cannot choose a collaboration forum area as it does not appear in the list of destinations available. 

    Personally I would only want these set up from the ACP and therefore do not need collaboration owners to have the ability to set these up.

    Best Wishes

     

  5. Hi Kevin

    Is there a way to set all new collaborations created in a specific category to be Unapproved meaning that they require mod/admin approval before they actually appear live for all to see? Or would that need to be done through Rules?

    Thanks

  6. Latest version of Collaboration installed on the Gold release of IPB 4

    When I enable the application I get

    Fatal error: Call to undefined method IPS\Member::collabs() in /home/polcom/public_html/dev/system/Theme/Theme.php(624) : eval()'d code on line 9257

    Disable it everything is fine again.

  7. You're correct. At the moment that kind of granularity is not built in. But I agree that it would be a good addition. You can expect to see that in an update.

    ​On that basis Kevin - this now meets every one of my requirements along with the promise of expanding rules to better connect Commerce with Collaborations. As you have confirmed these are features you will look to integrate I will now move forward and purchase the FULL version. 

    Thank you

  8. In addition there are a couple of things that are not copied exactly under models - not sure if these are bugs or not, one is if a background image is defined on the model it is not replicated on the others meaning you need to upload on each one, the next is the setting of having it as Open (without approval) to join the community area, it then makes it default to Open (approval required) on each new model again something which should be the same.

    I also noticed that the Default Member Title does not copy across when using the model

  9. Hi Kevin

    With the model arrangements is there a facility to take things one step further, for instance ... if in 'Category A' I have 'Area A' flagged as a model, within that model I have all the roles defined such as moderator for that area etc wit the permissions for them also defined. If I open that category up so that a member of a specific group is able to create a new area and they create 'Area B' prevent them from then editing things such as the 'manage roles' as ultimately I have defined a model and I want them all to be dealt with exactly the same. As its a model based approach I would like the facility to disable the manage roles or disable each of the permissions within manage roles from being granted on a category by category basis.

    Suggestion for the future unless of course I am missing something which is of course possible :-)

    Thanks

  10. Hi - will there be any way of selling the collaborations and specific features with upgrades etc to add additional features for example integrating it with Nexus to create products in nexus (sorry commerce) which allow the purchase of a new collaboration with addons for additional modules perhaps (Blogs, Downloads, Gallery etc) - Ive not really thought the detail through but it seems that could be a fantastic plus to what is already a great product.

  11. Sorry - one other quick question - is there also a way to display certain collaborations on the board index, I may have missed this in the sea of configurable options, possibly as a sidebar etc or would I just create re-direct links under the main forum module to link to the relevant collaboration?

  12. Hi - fantastic work here - using the demo in our test environment and it is fantastic. Can I ask if there is a way to move thread from a forum area to Collaboration just like you can move to another forum area? We are looking to utilise this for a specific section of our current community and it would be great to move the topics and replies into the collaboration environment?

    Thanks

×
×
  • Create New...