Diagnostics:
Textpattern version: 4.5.4 (r4919)
Last update: 2013-02-05 15:19:11/2012-12-05 08:55:43
Document root: /home/...
$path_to_site: /home/...
Textpattern path: /home/.../textpattern
Permanent link mode: section_title
upload_tmp_dir: /tmp
Temporary directory path: /tmp
Site URL: ...
PHP version: 5.3.18-1~dotdeb.0
GD Graphics Library: bundled (2.0.34 compatible); supported formats: GIF, JPG, PNG.
Server TZ: Europe/Moscow
Server local time: 2013-04-03 13:34:57
DST enabled?: 0
Automatically adjust DST setting?: 0
Time zone:  (+14400)
MySQL: 5.5.16-55-log
Locale: en_GB.UTF-8
Server: nginx/1.2.1
PHP server API: fpm-fcgi
RFC 2616 headers: 0
Server OS: Linux 2.6.32-5-amd64
Active plugins: cxc_templates-0.1.0(mod)
Admin-side theme: classic 4.5.4

Pre-flight check:
------------------------
Clean URLs are only supported on Apache, use at your own risk.
.htaccess file is missing
------------------------

Sergei

I post to both sections regularly and finally the 'articles' section shows life in the comments! I understand how to show it separately but would love to have it comb or mix in if that's possible.

Is it possible to tweak the code to control individual slide rest times?

Now go into your Txp Admin and go to the "Presentation/Forms" tab. Open up the " ap_twitter_head" form template and replace the top line with:-

<script src="<txp:site_url />_templates/aperture/assets/js/twitter2.js" type="text/javascript" charset="utf-8"></script>

That should do the trick.

If I see any problems I will post back in the appropriate theme forum with any fixes.

First of all you need to get an updated javascript from http://code.google.com/p/twitterjs/down … n=2&q=. Once you have unzipped the file upload the twitter2.js file which you will find in the "src" folder to the "site-design/js/" folder of your site and delete the existing "twitter-1.12.2.js" file.

Now go into Textpattern admin and open the "cb_twitter_head" form template. Replace the first line of the template with:-

<script src="<txp:site_url />site-design/js/twitter2.js" type="text/javascript" charset="utf-8"></script>

which will call the new javascript file.

That should crack the display problem but there is another minor change which Twitter has decided to force upon us. Open up the "cb_widget_twitter" form template and add the "@" sign in this line:-

<p class="follow"><a href="http://www.twitter.com/@<txp:variable name="widget_twitter_account_name" />">Follow us on Twitter</a></p>

That should make the "follow" link work properly.

<div id="twitter" class="widget widget_twitter">
<h3>Twitter</h3>

<div class="inner">
<div class="innerholder">

<ul id="twitter_update_list_woo_twitter-3"><li></li></ul>

</div> <!-- /.innerholder -->
</div> <!-- /.inner -->

<span class="shadow">&nbsp;</span>
<div class="controls">
<a class="down" href="#" title="Up/Down">DOWN</a>
</div> <!-- /.controls -->
    
<script type="text/javascript">
<!--//--><![CDATA[//><!--
    
    function twitterCallback2(twitters) {

      var statusHTML = [];
      for (var i=0; i<twitters.length; i++){
        var username = twitters[i].user.screen_name;
        var status = twitters[i].text.replace(/((https?|s?ftp|ssh)\:\/\/[^"\s\<\>]*[^.,;'">\:\s\<\>\)\]\!])/g, function(url) {
          return '<a href="'+url+'">'+url+'</a>';
        }).replace(/\B@([_a-z0-9]+)/ig, function(reply) {
          return  reply.charAt(0)+'<a href="http://twitter.com/'+reply.substring(1)+'">'+reply.substring(1)+'</a>';
        });
        statusHTML.push( '<li><span class="content">'+status+'</span> <a style="font-size:85%" class="time" href="http://twitter.com/'+username+'/statuses/'+twitters[i].id_str+'">'+relative_time(twitters[i].created_at)+'</a></li>' );
      }
      document.getElementById( 'twitter_update_list_woo_twitter-3').innerHTML = statusHTML.join( '' );
    }

    function relative_time(time_value) {
      var values = time_value.split( " " );
      time_value = values[1] + " " + values[2] + ", " + values[5] + " " + values[3];
      var parsed_date = Date.parse(time_value);
      var relative_to = (arguments.length > 1) ? arguments[1] : new Date();
      var delta = parseInt((relative_to.getTime() - parsed_date) / 1000);
      delta = delta + (relative_to.getTimezoneOffset() * 60);

      if (delta < 60) {
        return 'less than a minute ago';
      } else if(delta < 120) {
        return 'about a minute ago';
      } else if(delta < (60*60)) {
        return (parseInt(delta / 60)).toString() + ' minutes ago';
      } else if(delta < (120*60)) {
        return 'about an hour ago';
      } else if(delta < (24*60*60)) {
        return 'about ' + (parseInt(delta / 3600)).toString() + ' hours ago';
      } else if(delta < (48*60*60)) {
        return '1 day ago';
      } else {
        return (parseInt(delta / 86400)).toString() + ' days ago';
      }
    }
//-->!]]>
</script>
<script type="text/javascript" src="http://api.twitter.com/1/statuses/user_timeline/<txp:variable name="widget_twitter_user_name" />.json?callback=twitterCallback2&amp;count=<txp:variable name="widget_twitter_qty" />&amp;include_rts=t"></script>

</div> <!-- /#twitter -->

No it doesn't look a lot different does it? It's all in the detail. ;-)

Images in the slider are "broken" and I understand how but it's too confusing to figure out the fix.  The resulting HTML is busted.  Here's the HTML:

<img class="thumbnail" src="http://www.foodnewsie.com/sandbox/thumb.php?src=<img src=" http: www.dinarius.com foodnewsie sandbox images 1.jpg" alt> "&w=400h&h=267&q=95" alt="MoCo Farm&nbsp;Space" width="400" height="267" />"

There's several problems there, but what I can't straighten out is the part in the Form that makes all that happen. Here's the portion:

<img class="thumbnail" src="<txp:site_url />thumb.php?src=<txp:images><txp:image_url /></txp:images>&amp;w=400&amp;h=267&amp;q=95" alt="<txp:title />" width="400" height="267" />

I'm also worried that my sandbox creation method will lead to other problems, (website URL should NOT be www.dinarius.com) but I'll get to that later.  What should the ap_frontpage_slider_article Form say there?

This problem has been caused by changes within the Textpattern code which no longer allows the direct inclusion of function code within page/form templates. In order to fix this the function needs to be removed from the form template and converted into a plugin.

There are 2 things you will need to do to fix this on your site(s):-

First, you need to download, install and activate the new wet_if_comment_submitted plugin.

Next, you need to go into your Textpattern admin, go to the “Forms” tab and open the “tbs_tabs_script” form template. There is a block of PHP code at the top of the form that needs to be removed. You should be left with the following:-

<script type="text/javascript">
jQuery(document).ready(function(){

	var toDisplay = "<txp:if_comments_preview>#discuss<txp:else /><txp:wet_if_comment_submitted>#discuss<txp:else />#article</txp:wet_if_comment_submitted></txp:if_comments_preview>";

	// UL = .tbsTabs
	// Tab contents = .inside

	jQuery('.inside ul li:last-child').css('border-bottom','0px'); // remove last border-bottom from list in tab content
	jQuery('.inside > *').hide();
	jQuery(".tbsTabs li a[href='"+toDisplay+"']").addClass('selected'); // Add .selected class to designated tab on load
	jQuery('.inside '+toDisplay).show(); // Display designated tab contents on load

	jQuery('.tbsTabs li a').click(function(evt){ // Init Click funtion on Tabs

		var clicked_tab_ref = jQuery(this).attr('href'); // Store Href value

		jQuery(this).parent().parent().children('li').children('a').removeClass('selected'); //Remove selected from all tabs
		jQuery(this).addClass('selected');
		jQuery(this).parent().parent().parent().children('.inside').children('*').hide();

		jQuery('.inside ' + clicked_tab_ref).fadeIn(500);

		 evt.preventDefault();
	})
})
</script>

Save this and hopefully everything should be working properly again.

My thanks to morgant for pointing out the problem.

Typing any text gives this message: "Error: Invalid query string"

Here is the diagnostic log;
Textpattern version: 4.5.2 (r4197)
Last update: 2012-10-10 11:00:30/2012-10-09 11:00:42
Document root: /lala/prudens.com.au/www
$path_to_site: /lala/prudens.com.au/www
Textpattern path: /lala/prudens.com.au/www/textpattern
Permanent link mode: messy
upload_tmp_dir: /phptmp
Temporary directory path: /lala/prudens.com.au/www/textpattern/tmp
Site URL: prudens.com.au
PHP version: 5.2.17
GD Image Library: bundled (2.0.34 compatible); supported formats: GIF, JPG, PNG.
Server TZ: Australia/Melbourne
Server local time: 2012-10-18 15:21:03
DST enabled?: 1
Automatically adjust DST setting?: 1
Time zone: Australia/Sydney (36000)
MySQL: 5.5.27-rel28.1
Locale: en_GB.UTF-8
Server: Zeus/4.3
PHP server API: cgi-fcgi
RFC 2616 headers: 0
Server OS: Linux 2.6.32-5-amd64
Active plugins: an7_comments-0.5, cbs_category_list-0.9, glx_gravatar-2009.3, rss_auto_excerpt-0.5, smd_calendar-0.42c, smd_if-0.9, soo_page_numbers-0.2.7(mlp), zem_contact_lang-4.0.3.6, zem_contact_reborn-4.0.3.20, smd_pullquote-0.1a, yab_email-0.4, arc_twitter-1.0.3beta, pax_grep-0.2, tbs_variables-1.0(dele), tbs_widgets-1.0(dele), tru_tags-3.6(mod), upm_date_archive-0.2.5(mod), smd_bio-0.31, cxc_templates-0.1.0(mod), tbs_placeholder-1.0, smd_lib-0.3, esq_adminsplash-1.01(dele), smd_admin_themes-0.26
Admin-side theme: hive 4.5.2

Pre-flight check:
------------------------
The following PHP functions (which may be necessary to run Textpattern) are disabled on your server: posix_setegid, posix_seteuid, posix_setgid, posix_setpgid, posix_setsid, posix_setuid, posix_kill, pcntl_alarm, pcntl_exec, pcntl_fork, pcntl_getpriority, pcntl_setpriority, pcntl_signal, pcntl_wait, pcntl_waitpid, pcntl_wexitstatus, pcntl_wifexited, pcntl_wifsignaled, pcntl_wifstopped, pcntl_wstopsig, pcntl_wtermsig

I cannot recall what the setup was before it stopped working but am wondering could it be due to an upgrade of txp to v4.5.x?

Lee

If you need to import a theme on a site that is using an older version of Textpattern you will need to use the original version of the plugin which you can get here.

This does not apply to those themes using the “mem_templates” plugin.

Syntax error, unrecognized expression: [rel*=[pp_gall]]

Upon investigation I found that the Coda theme uses prettyPhoto.js (a lightbox implementation in jQuery), specifically looking for images with "rel='prettyPhoto[pp_gall]'". However, the jQuery selector doesn't quote the gallery name and since it contains square brackets which are special characters in selectors, it fails. Quoting it solves the issue and allows the lightbox to function correctly. Here's the diff for the fix:

@@ -128,7 +128,7 @@
                 // Build the gallery array
                 var images = new Array(), titles = new Array(), descriptions = new Array();
                 if(theGallery){
-                    $('a[rel*='+theGallery+']').each(function(i){
+                    $('a[rel*="'+theGallery+'"]').each(function(i){
                         if($(this)[0] === $(_self)[0]) setPosition = i; // Get the position in the set
                         images.push($(this).attr('href'));
                         titles.push($(this).find('img').attr('alt'));

Tag error: <txp:wet_if_comment_submitted> ->  Textpattern Warning: tag does not exist

This causes it to fail to select either the article or comments tabs, so the page appears to be missing all content (although clicking the article tab correctly shows the page). Naturally "wet_if_comment_submitted" is not actually a plug-in, but inline PHP in the 'tbs_tabs_script' form. I have "Allow PHP in pages?", "Allow PHP in articles?", and "Allow raw php?" all set to "Yes" in Textpattern's preferences.

Clearly what is happening is that even though the "wet_if_comment_submitted" function is defined, Textpattern isn't seeing it as a tag to run. Therefore, the javascript isn't able to properly set the ID of the tab element which it's supposed to be shown by default,  so it doesn't get shown.
Is this method of using "wet_if_comment_submitted" incompatible with more recent Textpattern versions?

Thanks in advance for any further insight you can provide. Naturally, I can change the logic to not check whether a comment was submitted (therefore showing the comments tab by default in that case), but would be best to retain that functionality.