Forum Activity for @tig

Simple Chat for Mobile Devices

Jamroom Developers

Looks like the code disables Simple Chat for mobile and tablet users.

I am quite interested in providing chat support on all devices (in order to replace a 3rd party chat function with Simple Chat) but I would like to know upfront if this requires a large development effort.

Thus, could someone summarize the technical reason(s) why Simple Chat is not trying to support mobile devices?
updated by @tig: 11/30/17 11:42:33PM

Dependent Listeners

Jamroom Developers

@brian - And with that all is well. The firing order is as desired and my functionality is working per design. Good as it gets, right?

Thanks for the tip.
updated by @tig: 08/29/17 10:08:51AM

Dependent Listeners

Jamroom Developers

(2017-08-29T17:37:29+01:00.0.72297300 : 0) ntCommentHierarchy_db_search_items_listener
(2017-08-29T17:37:29+01:00.0.72336300 : 0) jrComment_db_search_items_listener
(2017-08-29T17:37:30+01:00.0.90532900 : 0) ntCommentHierarchy_db_search_items_listener
(2017-08-29T17:37:30+01:00.0.90580800 : 0) jrComment_db_search_items_listener

@brian

The above is an edited cut from fdebug. I simply logged the entry into the functions to see the firing order. Seems no matter what I do with ntCommentHierarchy priority (set at 251 but I did try 249 just to be complete) the ntCommentHierarchy listener always fires before its jrComment counterpart. (I also verified jrComment has priority of 250.)

I have worked out another solution that is not sensitive to order, but for my own future knowledge I would like to exploit priority to emulate method overrides. Can you think of anything obvious that would explain how -ostensibly- a 251 priority listener runs before a 250 priority listener? If not, no worries since I have an alternate approach (albeit less efficient, ... ).

Thanks.

Dependent Listeners

Jamroom Developers

I created a module that logically -using an OO metaphor- is a subclass of jrComment. Accordingly I would like the listeners for jrComment to function first before the equivalent listeners in my module (the subclass of jrComment).

My particular concern lies with jrComment_db_search_items_listener. Threaded comments need to be ordered and jrComment_db_search_items_listener embeds the functionality for doing so.

It is of course not appealing for me to replicate the ordering logic (sorting twice) in my db_search_items_listener. I would much rather force my db_search_items_listener to engage after the jrComment_db_search_items_listener.

Thus my question: is there any mechanism for imposing a module dependency on listeners?

------------

( I created my module only to avoid making changes in jrComment. It would be trivial to just add my logic on the tail end of the jrComment listener. )

updated by @tig: 11/29/17 09:06:26AM

Configuring a Beta Test Environment

Installation and Configuration

@michael - Thanks for the confirmation. I will make my plans accordingly. Easily addressed.

Configuring a Beta Test Environment

Installation and Configuration

@michael - As usual, thanks for the wealth of information. I am sorry that I was not clear. What I seek to do is basic. I literally want to copy the code (not the data) from an existing site to a new site within a single jamroom hosted account. The existing site is production, the new site will be the development site. This is just an initial setup, not ongoing operation.

I have created the new site so the base code is there. All I want to do is copy code from the production site to the development site so that they start off identically (except, of course, for the data).

I can of course do this manually via SFTP. **And if that is the recommended approach I am good with it.** But if there is a better approach (one that does a server level copy rather than dealing with downloads and uploads) I of course would use it.

In short, is there an existing function that will server-level copy code (but not the data) from one jamroom hosted site (production) to another jamroom hosted site (development) within the same account?

And again, I appreciate the fact that you take time to answer our questions.

Configuring a Beta Test Environment

Installation and Configuration

@michael - How would I ensure the code is identical? I was misunderstanding I suppose but I thought the import was a one-step method to create an identical site. I would like to avoid synchronizing code via a massive SFTP cycle.

Configuring a Beta Test Environment

Installation and Configuration

@brian - Is there a way to create these sites without copying the database contents? It seems 'Import a Jamroom Site' will transfer the database contents.

Configuring a Beta Test Environment

Installation and Configuration

@brian - Thanks, that is exactly the advice I was looking for. Given that, with Jamroom hosting I could create a Beta site for verification and an Alpha site for development. All neatly contained in the same Jamroom hosting environment. Am I on the right track?

Configuring a Beta Test Environment

Installation and Configuration

Looking for advice on how to allow users to Beta test new changes to a site prior to going production. This is just the conventional Beta scenario. Imagine a new version of the site has been developed with changes to PHP, JS, CSS, templates, modules, etc. Want to have real users experience the new version for a few weeks. Once the Beta is over will migrate the changes to the production environment.

To wit, how should we configure jamroom to provide a production and a Beta test environment?

( Could not find this topic in the forum. )
updated by @tig: 11/24/17 09:14:56AM