Recent Updates have Removed Events
Using Jamroom
No worries - found it in a previous ticket.
Forum Activity for @paul
Recent Updates have Removed Events
Using Jamroom
Create a ticket with your admin login and we'll check it out.
Thanks
Recent Updates have Removed Events
Using Jamroom
Hi Zach
You needed to update the jrBlackSkin/jrEvent_item_index.tpl file to use the proper order_by value that's in the latest jrFollowMe/jrEvent_item_index.tpl
We've done that for you. Check your site out now.
Thanks
Cyber Monday - up to $200 off Jamroom Premium and Pro!
Announcements
Hi - Welcome back to Jamroom
This promotion runs until the 1st December but we normally can do a deal for old Jamroom4 customers wanting to move up should you not be able to take advantage of this offer.
Thanks
Paul
Documentation module stripping html
Using Jamroom
I think you'll need to put it inside a 'code' section.
hth
Contact Module
Jamroom Developers
The Simple Custom Forms module-
https://www.jamroom.net/the-jamroom-network/documentation/modules/2885/simple-custom-forms
Duplicates and 'follow_unique' in jrdiscussion_follow_topic
Jamroom Developers
Hi Tig
I cannot say for sure that no one else uses the Discussion module, but we typically get forum posts and support tickets about every other Jamroom module, but only queries about the Discussion module from you (NT), hence our assumption.
The Discussion module was originally sponsored by NT as upon migration to Jamroom, it was essential for you to have threaded comments/posts to discussion topics, which our Forum module doesn't support. If threaded posts are no longer a necessity, I would strongly suggest the going forward you use the Forum module instead, which provides the same functionality as the Discussion module but is more robust and has greater scalability.
hth
Duplicates and 'follow_unique' in jrdiscussion_follow_topic
Jamroom Developers
As, to our knowledge, you are the only site using the Discussion module, we actually fixed up your database table 'by hand' as that was a lot quicker and easier than writing repair code for the module (although the module code has been updated to work with the new table schema). Here is what we did -
1) Make a temporary jr_jrdiscussion_follow_topic_tmp table -
CREATE TABLE `jr_jrdiscussion_follow_topic_tmp` (
`follow_topic_id` int(11) unsigned NOT NULL DEFAULT '0',
`follow_user_id` int(11) unsigned NOT NULL DEFAULT '0',
`follow_created` int(11) unsigned NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
2) Copy only the unique values from the existing table to the temporary one -
INSERT INTO jr_jrdiscussion_follow_topic_tmp
SELECT follow_topic_id, follow_user_id, follow_created FROM jr_jrdiscussion_follow_topic GROUP BY follow_topic_id, follow_user_id
3) Make the follow_topic_id and follow_user_id keys as unique
4) Drop the original jr_jrdiscussion_follow_topic table
5) Rename the jr_jrdiscussion_follow_topic_tmp to jr_jrdiscussion_follow_topic
Duplicates and 'follow_unique' in jrdiscussion_follow_topic
Jamroom Developers
Hi Tig
Have fixed this up on your site.
The jr_jrdiscussion_follow_topic table unique index wasn't configured corrected. This is now done and all duplicate entries have been removed from the table. Also, the module code has been updated to use the table correctly.
See how it goes.
Note that if any of your users followed a topic during the few minutes whilst the table was being cleaned up, it may not have been stored, so they may need to 're-follow'.
Thanks
Paul
Duplicates and 'follow_unique' in jrdiscussion_follow_topic
Jamroom Developers
Checking this out - thanks.
