Forum Replies Created

Viewing 15 replies - 31 through 45 (of 109 total)
  • Plugin Author Bernhard Riedl

    (@neoxx)

    Hi Emil,

    There’s maybe another plugin which interferes or your theme does alter the post-loop (not in your tag.php, which looks fine to me).

    So to narrow the issue down, you should first deactivate all plugins and only activate TagPages. If the tagged pages still don’t show up on your archive pages, try to switch to one of WordPress bundled themes (e.g. TwentyTwelve or TwentyThirteen). – I’ve also tested TagPages with TwentyFourteen – which is currently under development – and it works fine.

    Hope that helps.

    My Best,
    Berny

    Plugin Author Bernhard Riedl

    (@neoxx)

    Hi bloggerHey,

    There are two things that come to mind:

    * as you’ve mentioned you’re probably missing a template-file. – you can find further infos here for archive.php and tag.php.
    * your permalink-setting for the tag-base may be not be ‘tag’, cf. http(s)://www.yourdomain.com/wp-admin/options-permalink.php

    If you’re still having troubles, you could activate the default theme in order to check if for example another plugin interferes.

    Greetz,
    Berny

    Plugin Author Bernhard Riedl

    (@neoxx)

    hi wombii,

    sure thing, you need to pass the timezone of choice as parameter. – try to input the following code in the widget:

    global $timezonecalculator;
    
    $timezonecalculator->output(array('timezones' => array('Australia/Perth')));

    there’s a list of all available parameters in the other notes section.

    greetz,
    berny

    Plugin Author Bernhard Riedl

    (@neoxx)

    Hi lawrenceit,

    Actually that’s not a problem with TagPages. 😉

    Navigational pages which are not relevant to search engines should always be set to noindex for all bots because they do only create a benefit for users and – as you say – contain duplicate content.

    I recommend to either use a plugin which generates a robots.txt or you can always create a robots.txt-file by hand in the root of your public web-folder and block the tag-tree like that:

    Disallow: /tag/

    In addition you can speed up the process of cleaning your Google Index with Google Webmaster Tools if you remove the whole tree.

    Greetz,
    Berny

    Plugin Author Bernhard Riedl

    (@neoxx)

    hi 1978tree,

    you can add a function-call to the_tags as described in the faqs.

    the file which you need to edit depends on the theme you’re using. – here’s an overview on theme development. – in case you’re using a custom theme, you can also contact the theme developer for help.

    greetz,
    berny

    Plugin Author Bernhard Riedl

    (@neoxx)

    Hi khlitoshi,

    1. Select the TimeZone which you want to edit in the Drag and Drop Layout
    2. Click on the blue arrow to open the details of the entry
    3. Unselect Use DB Abbreviations
    4. Enter your descriptions in the fields Abbreviation Standard and Abbreviation Daylightsaving

    Greetz,
    Berny

    Plugin Author Bernhard Riedl

    (@neoxx)

    hi rusola,

    the search-functionality in wordpress does include the post-title and the post-content but not any taxonomies like post-tags.

    if you want to include tags in your full-text search results, you have to use an additional plugin or manipulate the search-query with the filter posts_search which is provided in wp-includes/query.php.

    $search = apply_filters_ref_array('posts_search', array( $search, &$this ) );

    greetz,
    berny

    Thread Starter Bernhard Riedl

    (@neoxx)

    Hi RavanH,

    Your plugin currently supplies the XML-sitemap for about 10 apps in our realm. 🙂

    With “exclude by post meta key/value” I mean that giving a post or page a custom meta key like “sitemap_exclude” and value “yes” (or 1) would make that post/page be excluded from the sitemap…

    I do not have time the coming weeks to work on it but as soon as any of this is in the dev version, I’ll let you know. Maybe send me a reminder if you don’t hear from me for too long 😉

    Did you have time to look into my feature request?

    Greetz,
    Berny

    Hi kremuwa,

    Speaking for TagPages, you probably need to turn on the tags-widget in the Screen Options or disable other plugins which may cause a conflict.

    Greetz,
    Berny

    Thread Starter Bernhard Riedl

    (@neoxx)

    Hi Mark,

    Good news. 🙂 After compiling and updating APC to version 3.1.9 and a running a few tests during the last week everything works fine with your plugin 2.0.2 (stable).

    I can still only speculate because the results are hard to reproduce, but it seems that either APC 3.1.3p1 itself or the combination of Debian Squeeze with PHP 5.3.3-7 and APC 3.1.3p1 caused this issue.

    Greetz,
    Berny

    Thread Starter Bernhard Riedl

    (@neoxx)

    Hi Mark,

    Thanks for your feedback and the update. – I’ve installed 2.0.2b on our staging-server.

    According to the cache-entries alloptions is NULL now. – Thus, for example, changing the timezone-setting – as described before – works, though without any caching.

    fyi: As you’ve pumped the minimum-requirement, you should probably also adopt the error-message ‘The APC object cache backend requires PHP 5.2 or higher’ to 5.2.4.

    Today I had the chance to test a similar setup on a windows server with your plugin 2.0.2 and APC 3.1.6. – It seems that there all cache-entries get updated just fine.

    I thought I can rule the APC cache itself out, but maybe after all it’s a bug in APC. – The behavior is confusing and errors are hard to reproduce…

    So first of all, I will request an update of APC on our Debian staging-server and get back to you with further results.

    Greetz,
    Berny

    Thread Starter Bernhard Riedl

    (@neoxx)

    After some tests, it seems that for posts, pages, etc. the apc-cache-entry is updated on every change. Moreover, a call to update_option() works correctly as the following code delivers a fresh result if called for example in the init-hook.

    <?php
    $rand=rand();
    
    update_option('bogus', $rand);
    echo(get_option('bogus'));
    ?>

    Though, I still have the issue in the WordPress Admin Menu and now it really gets strange: The settings TimeZone, Date Format, Time Format, Week Starts On and Site language on https://mydomain.com/wp-admin/options-general.php are written to the database on update but the cache is not updated. Other options on the same page like Site Title or Tagline are updated correctly in the database and the cache.

    I’ve also tested my plugins which use the WP 2.7 Settings-API and all of them update all options just fine in the database and the cache.

    So I can rule out a bug in APC itself and start thinking that this issue is also not related with the APC Object Cache Backend plugin but rather caused by a bug in WordPress core.

    Could anybody please test this behavior and provide me with some feedback.

    greetz,
    Berny

    Thread Starter Bernhard Riedl

    (@neoxx)

    Hi RavanH,

    That’s a sound idea. – I will forward your plans to my SEO guys who will be happy about it. 🙂

    Greetz,
    Berny

    Thread Starter Bernhard Riedl

    (@neoxx)

    Hi RavanH,

    I’ve been using WP a long time and the permalink structure /%postname%/ has always caused problems. Not only for plugins but other (even WP internal) functionality too. In fact, I am surprised that up to this day, that permalink structure is still even allowed…

    I agree with you on that. – From a coder’s point of view, I also prefer order and hierarchy in pages, posts, archives. Nevertheless, as you’ve mentioned there are reasons and for which our SEO department needs such a link-‘structure’.

    So I would like to ask you to do a test upgrade to the development version to see if that trailing slash still occurs.

    I installed your dev-version on our staging-server after having a look onto your source code. – Nice idea. – Your function also protects other ‘generated files’ from being trail-slashed and it works great over here. 🙂

    I’ll take the exclude filter in to consideration too. It’s not a bad idea and will likely make it into the development version soon 🙂 Would you mind if it would be in the form of a post meta key/value to exclude a posts from the sitemap?

    Perfect and thanks. I’m not sure what you mean by post meta key/value? Or do you also plan to block pages by slug and not only by Ids?

    Greetz,
    Berny

    @huyz: thanks for the patch. 🙂

Viewing 15 replies - 31 through 45 (of 109 total)