Russ
Well-known member
Yoskaldyr updated CMF Threads - Thread Tweaks and Nested Comments with a new update entry:
CMF Threads 1.0.1 Released
Read the rest of this update entry...
What option was added?
Yoskaldyr updated CMF Threads - Thread Tweaks and Nested Comments with a new update entry:
CMF Threads 1.0.1 Released
Read the rest of this update entry...
Yes.What happens if this add-on is uninstalled? Do the comments revert to regular topic responses?
Leave as-is standard "Reply" button for nested comments and add "Comment" button (default behavior is replacing "Reply" with "Comment").What option was added?
Not exactly.Just for understanding - if i comment the 1. Post on a Thread it creates always a normal, regular Posting, if i comment later Posts in a Thread the appear as comments correctly ?
that is not correct behavior. It is definitely bug of your installation - maybe incompatibility issues with other add-ons or with your customized templates....and one other Thing. If i comment a post in Thread (in the middle of a thread) the comment appears after directly under all Posts of that page, after i reload the thread page the comment is correctly oriented. But this i think will be little confusing for users, because it Looks that the comments directly after posting it is attached to the wrong post...
It will be good. If it possible to fix on side of my add-on I will fix it as soon as possible.Will try to find out the conflicts in Detail.
This add-on not throws such errors.NGINX 405 Not Allowed
You server configuration is not enough for rebuilding 250 threads in the one batch (default value) in 2 minutes.However when I try rebuilding the index it starts and gets through about 100,000 threads and then throws the following error. "Fatal error: Maximum execution time of 120 seconds exceeded in /home/satguys/public_html/xen/library/CMF/Thread/Model/Extend/Post.php on line 453"
You have to enable add-on again. And start thread counter rebuild again with decreased "Items to process per page:" value. It will help you.I have had to disable it for now.
Your server definitely has some issues with configuration. Because on installation process my add-on does only small database modifications. These modifications usually run a few seconds and do not run longer than execution time limit on your server (120 sec). And if such database modifications run longer that you may have a problems with any add-ons that alter database tables.With the error it does appear it actually installed.
I hope all database tables is altered correctly on previous install. Better enable add-on and upgrade add-on with the same xml file. Because proper template rebuilding on installation process is neededYou have to enable add-on again
<xen:if is="{$message.postbitType}"><xen:if hascontent="true"><em class="userTitle" itemprop="title"><xen:contentcheck>{xen:helper userTitle, $message, 1, 1}</xen:contentcheck></em></xen:if></xen:if>
<xen:if is="{$messagePosterHtml}">
{xen:raw $messagePosterHtml}
<xen:else />
<xen:username user="$message" class="poster" rich="true" />
</xen:if>
@Arvin, All can be done with template edits
you can add this code in message_simple template
right afterHTML:<xen:if is="{$message.postbitType}"><xen:if hascontent="true"><em class="userTitle" itemprop="title"><xen:contentcheck>{xen:helper userTitle, $message, 1, 1}</xen:contentcheck></em></xen:if></xen:if>
HTML:<xen:if is="{$messagePosterHtml}"> {xen:raw $messagePosterHtml} <xen:else /> <xen:username user="$message" class="poster" rich="true" /> </xen:if>
<xen:require css="message_simple.css" />
<xen:require css="bb_code.css" />
<li id="{$messageId}" class="primaryContent messageSimple {xen:if $message.isDeleted, 'deleted'} {xen:if '{$message.is_staff}', 'staff'} {xen:if $message.isIgnored, ignored}" data-author="{$message.username}">
<xen:avatar user="$message" size="s" img="true" />
<div class="messageInfo">
<xen:if hascontent="true">
<ul class="messageNotices">
<xen:contentcheck>
<xen:hook name="message_simple_notices" params="{xen:array 'message={$message}'}">
<xen:if is="{$message.warning_message}">
<li class="warningNotice"><span class="icon Tooltip" title="{xen:phrase warning}" data-tipclass="iconTip flipped"></span>{$message.warning_message}</li>
</xen:if>
<xen:if is="{$message.isDeleted}">
<li class="deletedNotice"><span class="icon Tooltip" title="{xen:phrase deleted}" data-tipclass="iconTip flipped"></span>{xen:phrase this_message_has_been_removed_from_public_view}</li>
<xen:elseif is="{$message.isModerated}" />
<li class="moderatedNotice"><span class="icon Tooltip" title="{xen:phrase awaiting_moderation}" data-tipclass="iconTip flipped"></span>{xen:phrase this_message_is_awaiting_moderator_approval_and_is_invisible_to_normal}</li>
</xen:if>
<xen:if is="{$message.isIgnored}">
<li>{xen:phrase you_are_ignoring_content_by_this_member} <a href="javascript:" class="jsOnly DisplayIgnoredContent">{xen:phrase show_ignored_content}</a></li>
</xen:if>
</xen:hook>
</xen:contentcheck>
</ul>
</xen:if>
<div class="messageContent">
<xen:username user="$message" class="poster" rich="true" />
<article><blockquote class="ugc baseHtml{xen:if $message.isIgnored, ' ignored'}">{xen:helper bodyText, $message.message}</blockquote></article>
</div>
{xen:raw $messageAfterTemplate}
</div>
</li>
We use essential cookies to make this site work, and optional cookies to enhance your experience.