ajax error in outlink collection

when clicking on a link. A box would pop up, state the error, then disappear.

I tracked it down to using the zdstatistics plugin. There may be some incompatibility with another plugin, or more likely newer versions of WordPress.

Deactivating the zdstatistics plugin fixed the error.

Since I have started using Piwik to track referring links and keywords there is no reason to use a stats plugin like zdstatistics or Google Analytics anyway.

This should be a great way to get easy backlinks to your blog.

So I tried this with a Twitter account.

Unfortunately, Links Alpha insists on making Twitter posts using a url shortener. The Links Alpha help guide, which is not very helpful, indicates that one can use their url shortener account to get stats of clicks through their link. All you have to do is enter your bit.ly account information.

The problem is I did not do this. I did not want shortened links. Rather, straight links from Twitter to my blog for maximum seo benefit.

Links Alpha used its own url shortener (not bit.ly) anyway.

So I found another WordPress plugin called WP to Twitter. Takes a little bit to setup through Twitter, but the instructions are clear and easy to follow.

WP to Twitter worked perfectly. My WordPress blog posts saw the title of the post immediately appear on Twitter, with a direct link back to my blog post.

But now the question is can Twitter be set to not no-follow links in Tweets?

Syndicate Kahuna – $67 per month

Notes: Put links within the article using the special token. There are no author resource boxes.

SEO Linkvine – $67 per month

Niche Press Platinum – $67 per month

Article Ranks – $39 per month or there is a pay as go option where each article costs $2 and a minimum deposit of $20 is required.

Notes: Put links within the article. There are no author resource boxes. The divider between spinning options is ‘~’ instead of ‘|’ as used with most spinning programs, so a search and replace needs to be done when copying from another program.

Important: Based on my experience some of the sites in this network have good rankings. The quality appears to be better than some other services.

Submit Eaze – $78.95 one time fee.

This software will automatically create accounts for you at article sites. You can then add your spin ready article to the software and it will spin the article title, article body, and author resource box – and automatically submit your unique articles to the article sites. You can also manually add as many article sites as you want to submit uniquely spun articles yourself. Must have software for the price. (Also includes ability to quickly submit your site to over a thousand directory sites.)

TrafficKaboom – $497 yearly or $147 every 3 months.

I believe this is by the owners of Syndicate Kahuna (Traffic Kahuna) and I think some of the ‘testimonials’ are by that “TK” system. It is not clear how different Kaboom is.

I decided not to try this service because of the high $147 entry point just to try it, a stupid name, and a bogus scarcity of being limited to 500 members. Looks more like a pitch for quick cash rather than an ongoing service.

Not Recommended:

Articles Crush – $47 per month.

Note: Links within the article are not allowed. Must put links in an author resource box.

Horrible experience. They put the wrong author on the article plus there were other problems. The owner was an incredible jerk and quite inhospitable to a number of customers. Stay away from this if they’re still in business.

SEO Link Machine – $37 per month.

Did not try this service although very tempted at the price. Offers article spinning and a drip feed.

The problems: This is a private blog network of new, no value, PR0, .info blogs, owned by one person. The comments for the service indicated he was really struggling trying to answer if the blogs were on unique C classes – not sure if he actually ever answered that. Plus someone posted a link to a couple blogs and the content on them was absolutely horrible.

No quality control and I did not want to be associated with that even to try it out. With one owner the entire network could be gone tomorrow. But maybe in the future this will look better.

Testing of the plugin with new WordPress 3.0 (using the Flexibility theme), shows that the plugin is now causing RSS feeds to not validate. Once the plugin is deactivated, the RSS feed validates. Validation was done with FeedValidator.org.

1. Within your cpanel click to add a new subdomain.

2. Call the subdomain * (yes, just an asterisk).

3. For the document root use the root domain (public_html). If the dynamic subdomains are for an add-on domain, then the document root will be public_html/youraddondomain.com.

That’s it.

Now, you can refer to a subdomain and it is automatically created on the fly. Such as using the WordPress WP subdomains plugin to create subdomains out of pages.

Yep. Works like a charm.

Instead of encouraging such spam, or having to moderate comments to delete spammy name links, why not simply delete the option to submit a website?

Our point of reference is the Mandigo theme, which we love, but this procedure should be universal across Wordpress blogs.

What you want to do is from the Theme Editor find the comments.php file.

About 3/4 of the way down there will be a section where you see the input requests if someone is not logged into your blog. The requests ask for the person’s name, email address, and website url.

Here is the code requesting the url:

<p><input type="text" name="url" id="url" value="<? php echo $comment_author_url; ?> "size="22" tabindex="3" /> 
	<label for="url"><small><?php _e('Website', 'mandigo'); ?></small></label></p>

Simply delete this code. Problem solved and it will not affect your blog because this is not a required field (unlike the name and email fields.)

Now, the only way a spammer can leave a link is if they post a link in the comments portion of the field. By moderating the discussion so that any comments are held if their contain one or more links, the spammer is stopped cold.

Posts can be associated with categories. Pages cannot.

If you associate a post with a category, and only have that one post for the category, then it can look like a page for website linking. Normally, each page can be linked in the sidebar, but each post cannot. Instead, the category for the post can be linked, or a plugin can be installed that might, for instance, display the last 5 posts. But if you want a table of contents that is harder with posts than with pages.

Pages can have subpages. That is, like a directory structure there can be subdirectories. Posts cannot.

Consider the Michael Jackson Funeral Website. Along the right-side of the page is a menu. Everything under ‘Memorabilia’ is a page. Everything under ‘Topics’ is a post. Each page displays one page of information. Each link under Topics displays the various posts associated with that category. There could be subpages listed under each page, but a decision was made not to clutter the menu with subpage listings.

Also, not all pages are listed in the menu. You can select certain pages not to be displayed. That cannot be done with posts.

What is going on is that the normal default terms of Pages and Categories have been changed to make the menu more attractive for the website.

Also, by default only posts appear in the Wordpress blog’s rss feed. Pages do not. This means if you only use pages and not posts, then you do not have an rss feed.

If you want pages to appear in Wordpress rss feeds then you need a plugin called RSS Includes Pages. One undocumented issue with the plugin is that it will not work if you only have pages on your blog. What you need to do is create some posts, then this plugin will be able to add your blog pages to the rss feed.

Instead, people trying to access your site receive an ugly 403 Permission Denied error.

Very bad.

What is happening is that your web host is disabling access to the index.php in your blog’s main directory.

To quickly circumvent this problem while working matters out with your web host, you will need a copy of your index.php file. Since you will not be able to access or view the code in the one that has been disabled, copy an index.php file from another blog you have, or create a new blog on a new domain just so you can copy the text of a basic WordPress index.php file.

Then upload that file to your disabled blog, and call it index2.php.

Now, in your .htacess file add this line:

ErrorDocument 403 /index2.php

Problem solved. What will happen is that the index.php file that WordPress needs to function is still disabled and returns a 403 error. However, the .htaccess file now traps that error and instead of displaying an ugly error page, redirects all traffic to index2.php. Since index2.php just happens to have the code from index.php which displays WordPress pages, your WordPress blog will continue to be displayed.

Your web host may not be happy about the circumvention, but you may need to be creative to keep your site up and money-flowing while issues are resolved with your web host.

Here is the trick:

Within the html web page the header information for the blog is incorporated using this code:

<?php
require(’./wp-blog-header.php’);

include $_SERVER['DOCUMENT_ROOT'].”/wp-content/themes/YOURTHEME/header.php”;
?>

Similarly, footer information from the blog is inserted into the html page with this code:

<?php
require(’./wp-blog-header.php’);

include $_SERVER['DOCUMENT_ROOT'].”/wp-content/themes/YOURTHEME/footer.php”;
?>

Finally, even the sidebar from the blog is included, to add that final touch which makes the web page virtually indistinguishable from blog pages:

<?php
require(’./wp-blog-header.php’);

include $_SERVER['DOCUMENT_ROOT'].”/wp-content/themes/YOURTHEME/sidebar.php”;
?>

There is a downside, though, and that is getting better SEO from a static web page since only a default page title, and maybe a description, will be pulled in from the blog header.

This technique was done at Michael Jackson Funeral but then the static pages were replaced with WordPress pages due to these SEO concerns.