There’s several that give different output, this one for example

http://www.google-adsense-templates.co.uk/google-adsense-sitemap

Has the latest comments linked at the top and the posts at the bottom.

There’s a template that only shows the posts.

http://www.stallion-theme.com/sitemap

David

1) Want to create page called “XYZ Index”
2) This page contains only list of all Titles of my posts with each title hyper linking to its blog post
3)when I click on these hyperlink, need to travel to post page.
4) these lists of posts either can be taken from archive or category field.
5) My page should look just look like below:

> post 1
> post 2
> post 3
> post 4

If it’s a sitemap there’s built in sitemap Page templates.

Under Dashboard: Page >> Add New

On the right you can select various Page templates including sitemaps.

David

I want to create a page with indexing.

I used short code for [Archive] in my new page visual editor, but it is not working.
So please let me know the probable solution for this.

Thanks!

If you update to the latest version of WordPress the error will be gone.

I develop Stallion so it works in the latest two major versions of WordPress. Currently WordPress is at version 3.3.* so I’m checking Stallion works in WordPress 3.2.* and WordPress 3.3.* (it also works in WordPress 3.1.*, but if something broke in WordPress 3.1.* I wouldn’t fix it unless it was a simple fix).

When WordPress updates to WordPress 3.4 I’ll check WordPress 3.3 and WordPress 3.4 when working on updates. I’ve checked Stallion 7.1 with WordPress 3.4 beta releases and early release candidates and already updated some code in the current Stallion version.

David

After entering my Tran code I went to view the front page and saw the following error message
Dont know what it means or how to fix it;

Fatal error: Call to undefined function get_post_format() in /home/acoach5u/public_html/selfimprovementmastery/wp-content/themes/stallion-seo-theme/index.php on line 30
Can you assist?

Thank You

Think Jetpack is enqueing Jquery since I’m finding

<script type='text/javascript' src='http://www.talian-theme.co.uk/wp-includes/js/jquery/jquery.js?ver=1.7.1'></script>

Within the footer area of the test site, jquery-1.7.1.min.js is loaded by the slider and I’m assuming this is causing a conflict with jquery.js loaded within the footer.

A plugin would normally enqueue Jquery with code like this:

wp_enqueue_script( 'jquery' );

This is within Jetpack, but disabling it didn’t remove the script code, so guess it’s enqueued some other way.

Never played around with Jquery beyond copying it into the slider code, so don’t know if there’s a solution. Jquery.min is loaded in the head of the code, jquery.js is loaded in the footer. When I was creating the slider I tried to add it to the footer, but it didn’t work.

Two possible solutions.

1. Load jquery.js in the head instead of Jquery min via the slider code and hope it works for the slider and Jetpack. You’d have to disable the Jetpack Jquery as well most likely.

2. Disable Jetpacks jquery.js code and see what happens, jquery.min.js might be enough.

David

Edit: Adding

wp_deregister_script( 'jquery' );

Which de registers the the Jquery script.

To the bottom of jetpack.php fixes the slider issue, no idea if it breaks anything Jetpack wise.

The code is there, but the sliding isn’t working as it should, the sliding is javascript based. I would look at javascript files loaded by other plugins, I see a couple loaded in the footer area one for the stats and the other related to Jetpack. Try disabling plugins that load javascript files see if it fixes the issue.

Could be a simple case of conflicting javascript, one of the plugins use jQuery javascript code like the slider does.

If it is a plugin let me know which and I’ll see if I can find a work around.

David

If it is too much trouble, I do not mind nuking the site and starting again, but maybe it is something I do not see.

Also I did note, that one another site, wp-polls might conflict with the slideshow. Not a bit deal not using it anyway, was just a plugin that was installed but never used.