Viewing 26 posts - 1 through 26 (of 26 total)
  • Author
    Posts
  • #188030

    Hi,

    I hope you can help me with this, even if it seems, that it’s not the theme’s “fault”.

    I activated wp super cache today, everything’s just fine – so far.

    But the timestamp of the latest comments in the combo widget are wrong.
    A comment from today has a timestamp from 2012. Clicking on it, the comment itself has todays date.

    Any ideas how to fix that?

    Regards,

    Boris – http://www.hebammenblog.de

    #189137

    Hi, (small update)

    i did some further research, but found no solution or reason for that behavior. A new comment, that came in in the meantime it’s just fine now, but previous comments are still wrong dated.)

    What’s new though is, that here: http://www.hebammenblog.de/newsletter-abonnieren/ the widget is strangely arranged:
    “Most popular” is displayed on top of the widget, but all others like “recent” and so on are displayed below it.

    What kind of widget is it? Is it written in javascript? The caching plugin author says it must be dynamic to work properly. I think it is, but just to make sure, I thought I’d ask ;-)

    Any ideas, what’s going on here?

    Regards,

    Boris

    #189809

    Hey!

    The Newsletter widget breaks the entire javascript on that page because it includes an old jquery version (1.4.2) – you can find it in the source code if you search for

    
    <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
    

    Make sure that the newsletter widget does not load a custom version of jquery.js and the “recent”, etc. tabs should work again.

    Cheers!
    Peter

    #190161

    Hi Peter,

    thank you for the answer. The code is provided by clerverreach for integration of their services. I will ask, if they have an updated version. But what, if not? What can I do then?

    And: Is this relevant for those two pages, only, or does it also effect the confusion of dates e.g. on the homepage? The script from above is only on these two pages…

    Thanks.

    Boris

    #190515

    Hi!

    No, it will only affect the pages where you load the code – in your case the two pages.

    But what, if not? What can I do then?
    Maybe try to extract the html code and to copy/paste the form code into a text widget. JQuery 1.4.2 is a very old version (released on the 19.02.2010) and Sentence or any other newer theme simply won’t work with this outdated jquery version. On the other hand it’s also not easily possible to load several jquery versions on the same website and it would also slow down your website performance without any good reason…

    Best regards,
    Peter

    #190551

    Hi Peter,

    okay, I made the change and it worked.

    The thing, that’s still not working correctly is the timestamp of recent comments in the widget.
    The most recent comment is dated in 2012. When you click on it and have a look at the actual comment, you can see, that the correct date is this week.

    Any ideas?

    Regards,

    Boris

    #191388

    Hey!

    Do you use the avia_widget_time filter to change the time format? If yes this filter may affect (and break) the time of the comments list too. See following line in /wp-content/themes/sentence/framework/php/class-framework-widgets.php

    
    echo "<span class='news-time'>".get_the_time($time_format, $comment->comment_post_ID)." ".__('by','avia_framework')." ".$comment->comment_author."</span>";
    

    If you’re using this filter please post the filter code and I’ll modify it for you. If not try to deactivate the third party plugins – maybe a plugin breaks the comments time output.

    Best regards,
    Peter

    #191405

    Hi Peter,

    well, I am not aware of using any filter, and I did not modify any code in this file. I am using the theme “as is” in this case. I only integrated the widget in the theme backend. Thats all. (How do I identify, if the filter is active?)

    I just deactivated the WP super cache plugin and tested the widget by posting a new comment. Nothing changed. The Problem came with activation of this plugin, so I don’t think it is any other plugin.

    Any other ideas? (I could give you backend access, if that helps)

    Regards,

    Boris

    • This reply was modified 1 year ago by  Boris. Reason: additional question
    #192339

    Hi!

    Can you try clearing the WP Super Cache cache before deactivating it. It will still technically be “active” even after you’ve deactivated it because it keeps the cache in use.

    Cheers!
    Devin

    #192643

    Hi Devin,

    still all the same.

    What can I do now?
    Would it help to have a look at the database, where the date is stored? Where would that be?

    I really would love to solve this problem soon ;-(

    Regards,

    Boris

    #193784

    Hi!

    Please create me an admin account and post the login data as private reply – I’ll look into it.

    Regards,
    Peter

    #193886
    This reply has been marked as private.
    #195273

    Hi,

    got it? ;-)

    Boris

    #195737

    Hi!

    Yes but tbh I don’t know what’s going on on your server. I tried to modify the file here: http://www.hebammenblog.de/wp-admin/themes.php?page=scte-theme-editor&theme=sentence&file=%2Fframework%2Fphp%2Fclass-framework-widgets.php and replaced

    
    			echo '<div class="tab widget_tab_comments"><span>'.__('Comments', 'avia_framework').'</span></div>';
    			echo "<div class='tab_content'>";
    			avia_get_comment_list( array('number' => $posts, 'status' => 'approve', 'order' => 'DESC') );
    			echo "</div>";
    

    with

    
    /*
    			echo '<div class="tab widget_tab_comments"><span>'.__('Comments', 'avia_framework').'</span></div>';
    			echo "<div class='tab_content'>";
    			avia_get_comment_list( array('number' => $posts, 'status' => 'approve', 'order' => 'DESC') );
    			echo "</div>";
    */
    

    and this change should remove the comments tab completely (just for testing purposes) but nothing happens. It simply ignores all code changes and still shows the tab. I recommend to remove the old sentence folder from the themes directory – maybe it prevents the plugin to open the files of the right theme folder.

    Best regards,
    Peter

    #195754

    Hi Peter,

    ok I deleted the old sentence files.

    Just for you to know:

    I also modified the tagcloudpart of the box. But I think this should not be a problem. Here is what I did:
    Tagcloud Blasengrößenanpassung:
    Framework/php/class-framework-widgets.php
    wp_tag_cloud(‘smallest=10&largest=24&unit=px’);

    und:

    Tag-Cloudanpassung (Design)
    Custom css und layout.css
    .sidebar .tagcloud a {
    background-color: transparent;
    }
    Go into the css>layout.css file and on line 1742 delete the font size declaration so that its just:
    .tagcloud a{ padding:2px 8px; margin:0 1px 1px 0; display:block; float:left; border-style: solid; border-width: 1px; text-decoration: none; }

    Maybe you can have another look, now?

    Thx,

    Boris

    btw: cashing plugin is still active – will changing of code have an effect right away? Maybe you have to delete the cashe and activate preload again?

    • This reply was modified 1 year ago by  Boris.
    #196621

    Hi!

    I think the cache plugin is still activated because of the wp_config.php entry. Please open up the file and probably you’ll find following code in it

    
    define('WP_CACHE', true);
    

    Delete this line and upload the modified wp_config.php – this ´should force WP to deactivate the cache.

    Regards,
    Peter

    #196644

    Hi Peter,

    done. I uninstalled the plugin completely following these simple instructions: http://wordpress.org/plugins/wp-super-cache/other_notes/

    The problem is still there, even when posting a new comment.

    Regards,

    Boris

    #196948
    This reply has been marked as private.
    #198034

    Hi!

    Have you ever checked with your hosting provider to see if they have any server side caching or anything like that? It might be worth a check with how many issues have been happening.

    Otherwise I’ve tagged the topic for Peter again as he seems to be most familiar with it at this point.

    Best regards,
    Devin

    #198090

    Hi Devin, Peter,

    I just checked that: They said, that caching is not available for shared hosting customers. So I can answer your question with: no! ;-)

    Hope we can solve this, soon. Quite a weired problem…

    Regards,

    Boris

    #198543

    Hey!

    Ich habe beim Testen anscheinend einen Syntax error in die wp-content/themes/sentence/framework/php/class-framework-widgets.php eingebaut und jetzt ist die Seite nicht mehr erreichbar. Bitte sendet mir auch die ftp Daten, damit ich den Code effizienter bearbeiten und updaten kann. Ansonsten ist die Seite jedes mal down, wenn ich einen kleinen Syntaxfehler mache.

    Regards,
    Peter

    #198559
    This reply has been marked as private.
    #198896

    Hi!

    Ok, Problem behoben und gefunden. Ich habe folgende Zeile

    
    echo "<span class='news-time'>".get_the_time($time_format, $comment->comment_post_ID)." ".__('by','avia_framework')." ".$comment->comment_author."</span>";
    

    gegen

    
    		echo "<span class='news-time'>";
    		comment_date($time_format, $comment->comment_ID);
    		echo " ".__('by','avia_framework')." ".$comment->comment_author."</span>";
    

    ersetzt und jetzt scheint die Funktion den richtigen Wert auszugeben.

    Regards,
    Peter

    #198930

    Hi Peter,

    wow! Super und endlich! ;-) Hab gar nicht mehr an den Erfolg geglaubt…

    Kannst Du sagen, woran es lag? Kann das Caching-Plugin das verursacht haben?
    Hast DU Originalcode wieder hergestellt, oder eine Anpassung gemacht? Welche und warum?
    Je besser ich das verstehe, kann ich bei Wiederauftauchen selbst anpacken…

    Ich würde das Plugin nämlich gerne wieder aktivieren – soll ich? ;-)

    Auf jeden Fall: Danke für die Hilfe. Das war ja ein echter Brocken!

    Beste Grüße

    Boris

    #198942

    Hey!

    Nein, ich weiß leider nicht woran es lag – ich habe einfach 2-3 andere Funktionen durchprobiert und die comment_date() Funktion hat dann funktioniert. Vielleicht wurde die Datumsstruktur in der Datenbank geändert aber genau weiß ich das nicht. Ich habe den Originalcode wie hier beschrieben: http://www.kriesi.at/support/topic/combo-widget-shows-wrong-last-comment-timestamp-after-wp-super-cache-setup/#post-198896 verändert.

    Das Plugin WP Cache kannst du mAn wieder aktivieren und je nachdem ob die Datumsanzeige dann noch immer funktioniert kannst du es auch aktiviert lassen. Als Alternative bietet sich auch W3TC an.

    Regards,
    Peter

    #199094

    Danke! Werde erstmal mit W3TC testen, hatte das eh also Alternative auf dem Schirm!

    Danke! ;-)

    Gruß

    Boris

Viewing 26 posts - 1 through 26 (of 26 total)

The topic ‘Combo Widget shows wrong last comment timestamp after WP Super Cache Setup’ is closed to new replies.