Forum Activity for @brian

brian
@brian
10/01/17 04:35:06PM
10,149 posts

removing home from index page title
Installation and Configuration

soaringeagle:
entire acp and backend is white screens

You messed up the template - smarty syntax error. Look in data/logs/error_log for the reason and line number.
brian
@brian
10/01/17 04:34:12PM
10,149 posts

Odd Problems
Jamroom Developers

I'm going to guess that is coincidental - I logged in via SSH and I see that the DB's are different. One thing to check is that you've not hardcoded any domains in templates.

We have a lot of users that are using threaded comments, and I'm not aware of any issues with it, so I'm not sure what to recommend without digging into it myself. If you're running any custom modules that also listen for db_create_item, you might try temporarily disabling them. One thing to know about events, is that each module can change the array of data that comes into the listener - i.e. a module that has a higher priority than another module could change the $_data coming in to another module that is lower in priority.

Also - check to see if the issue is only happening to comments on the Discussion module versus other modules (say a blog post) - if that is the case, then the Discussion module could be changing things via a listener.
brian
@brian
10/01/17 04:26:26PM
10,149 posts

removing home from index page title
Installation and Configuration

I think there is likely a {jrCore_page_title} call in your meta.tpl file, which is being included by your header.tpl file - so that is being called AFTER the one you've added. To get around this, you need to pass the title into the include. So get rid of the jrCore_page_title you added, and change this:

{jrCore_include template="header.tpl"}

To this:
{jrCore_include template="header.tpl" title="Dreadlocks Natural Dreads"}

Then, in your meta.tpl file change this:
<title>{$page_title|default:"`$default_title`"|capitalize} | {$_conf.jrCore_system_name}</title>

To this:
{if isset($title)}
<title>{$title}</title>
{else}
<title>{$page_title|default:"`$default_title`"|capitalize} | {$_conf.jrCore_system_name}</title>
{/if]

That way you can just add title= to any {include} call for the header and it gets set.
updated by @brian: 10/01/17 04:26:55PM
brian
@brian
10/01/17 04:19:36PM
10,149 posts

removing home from index page title
Installation and Configuration

Then use the system name variable:

{jrCore_page_title title=$_conf.jrCore_system_name}

updated by @brian: 10/01/17 04:19:59PM
brian
@brian
10/01/17 04:18:13PM
10,149 posts

Odd Problems
Jamroom Developers

TiG:
@brian

Will check on that, but note that the Beta site is virgin. I simply created the new name and ran the initialization. Never even signed on to it because attention turned to the comments on production. No files uploaded, nothing configured.

Did you create using our hosting tools here?
brian
@brian
10/01/17 04:17:43PM
10,149 posts

Jamroom 6.1 has been released!
Announcements

Yep - you should be good.
brian
@brian
10/01/17 04:12:57PM
10,149 posts

Odd Problems
Jamroom Developers

Make sure your beta site is not configured to use your production database in data/config/config.php.
brian
@brian
10/01/17 04:06:11PM
10,149 posts

removing home from index page title
Installation and Configuration

Yes - and you made sure there was not ANOTHER call to jrCore_page_title after it? And reset caches? I know for sure it works - we use it just like that here on jamroom.net.
brian
@brian
10/01/17 04:01:58PM
10,149 posts

FoxyCart - currently configured on a test gateway
Jamroom Developers

dm:
I changed it, however there is an error when trying to purchase. Check it out http://tuneport.net

"jrAudio-1 is not a valid downloadable product code for this category."

Make sure and check out our FoxyCart documentation - it sounds like you have configured FoxyCart to handle downloads, which you do not wan to use.

https://www.jamroom.net/the-jamroom-network/documentation/modules/205/foxycart-ecommerce
brian
@brian
10/01/17 03:56:38PM
10,149 posts

Odd Problems
Jamroom Developers

TiG:
@brian

Understood. The test case is not the first item. It is actually a reply to the second item (i.e. a reply to 2.1).

Note that the data is in the database - it just does not make it to $_data all the time.

Hmmm.. The db_create_item even always passes to the event listeners the data it receives, and the only place I don't see the comment_parent_id or comment_thread_id in the data is if comment threading is enabled, and it's the first comment.

I assume you have threading on? The first example you show is comment _item_id 34677, which is a new comment. The second one is a follow up on comment _item_id 548517, and should be threaded one indent off of 548598. So from here it looks correct.
  102