Luigi Cavalieri

Hello,
thank you very much for your report!

Please, update to SiteTree 6.0.3.

Regards,
Luigi

Grazie!

Hello,
the bullets don’t show up because the theme builder installed on your site acts on the ::marker pseudo-element of the list’s items.

A workaround is to use the following CSS rule:

.site-tree-list li::marker {
    color: #734b63;
}

Regards,
Luigi

Hello,
into which kind of sitemap would you like to list your posts?

If it’s a Site Tree (HTML Site Map), yes, it has a limited capacity. This is due mostly to guaranty a better user experience.

For a large Site Tree like the one I have seen on your website, I suggest to split it into multiple pages. SiteTree Pro has built-in pagination abilities.

If you need further help, you can contact me directly (https://luigicavalieri.com/sitetree/help/), too.

Regards,
Luigi

• This reply was modified 4 years, 1 month ago by Yui.
• This reply was modified 4 years, 1 month ago by Luigi Cavalieri.
• This reply was modified 4 years, 1 month ago by Luigi Cavalieri.

Thank you Pascal!

It’s some time, now, that I have decided there will not be further updates in the near future. For the few people that might have awaken the behaviour over-detailed above, the code down here is the workaround.

# Replace the function SiteTree::append_sitemap(), defined in
# sitetree/core/sitetree.class.php, with this one.

public function append_sitemap( $the_content ) {
  if ( in_the_loop() ) {
    // Paste here the body, without return value, of
    // the old version of SiteTree::append_sitemap()
  }

  return $the_content;
}

Just an aside: when the plugin behaves as described, it is very likely that usability hasn’t been taken enough into consideration, and that the real bug to be fixed might be already there, in the organisation of the content.

I was hoping it didn’t pop up before the next release but here we are.

Due to the kind of bug and the page where it turns on, it goes almost under the category of Edge Cases, so, I piled the fix on those that will be included in version 1.6.

Thank you anyway for the report.

P.S. The WP_Query class is just one of the tools to create multiple Loops, not always the best choice.

Because of the way SiteTree detects the page where to show the archive, this issue is caused or by a conflict with another plugin or by a bug in the active theme.

Anyway, a link to the website?

I understand what you are writing and what you are pointing out is one of the reasons why with every version I’m making the plugin more error aware.

However, this specific issue can’t be easily traced and debugged with just a snippet of code (otherwise I would have wrote it down from the start) and because it doesn’t related to the plugin itself, it requires the debugging of your WordPress installation to be fixed.

After you have deactivated the other plugins, try to deactivate and reactivare SiteTree (this will force the rewrite rules to flush) but, as suggested before, It isn’t a plugin related issue, there’s a conflict or a misconfiguration in your setup.

Hi,
there’s a plugin you are using or a rewrite rule hardcoded in your theme that forces a trailing slash in the Sitemap URL. If you fix it, the Sitemap will show up flawlessly.

Hi,
there are no more issues with the Image Sitemap — further improved with the latest release (1.5). The encoding problems were definitely fixed with version 1.4.3.

Its usually better to have a single sitemap to submit both URLs and Images.
I think that with version 1.6 the option to turn off the Image Sitemap will be completely removed.

I don’t know the Video Sitemap plugin you are linking but there should’t be compatibility issues.

For those of you reading this: version 1.5.1 fixes the issues reported. More details in this post and the changelog.

Hi,
what does you mean exactly with “destroyed”? Have you lost just some of them or the whole list of exclusions? Does the issue affect both posts and pages?
Are there any other customisations you did and now are missing?

Right now, I can’t confirm any bug. I tested one more time the upgrade from version 1.4.3 and it succeed.

I don’t recommend running versions older than the current one in any case.

However, your old settings haven’t been lost. From now on, SiteTree makes an automatic backup copy of all your settings and back-end data before performing the upgrade.

To be sure there isn’t a bug, you could send me a copy of the data the plugin is currently working with (but via the contact form on the website). To do so:

– Upgrade to version 1.5
– Place the following code at the beginning of the functions.php file in your theme, just after the opening <?php tag:

add_action( 'wp_footer', create_function( '',
    "echo @serialize( get_option( '_sitetree_backup' ) ) . "
  . "'<br><br>' . @serialize( get_option( 'sitetree' ) );"
));

– Visit a web page of your site
– Send me all the text that has been printed out in the footer of the page.

Then, you can delete the code from the functions.php file.

Hi,
once upgraded to version 1.5, try to rebuild the sitemap (clicking on the “Rebuild” button), visit it and then, check the error log file of your server. Are there any errors related to SiteTree?

I need the actual URL to your sitemap, too.