“Failed to enable constraints. One or more rows  contain values violating non-null, unique, or foreign-key  constraints.”

Talk about annoying – this took me the better part of an hour and half to figure out where this error was coming from. Quite descriptive if you ask me <rolling eyes>. It’s as useful as this:

As with any bug the more information you can get on it – the better. The code I put together thanks to a tip from Roy Osherove’s Blog gets into the DataSet object to see which column is actually throwing the error.

foreach( DataTable table in dataSet.Tables)
{
if (table.HasErrors)
{
     foreach ( var error in table.GetErrors())
     {
         if (error.HasErrors)
             throw (new Exception( error.RowError));
     }
}
}

This produced a much more descriptive error that allowed me to track down the problem:

Shendy.

I dedicated some time today (ended up taking 10 minutes), to figure this out.

The default for WordPress URLs is http://www.iamshendy.ca?cat=10, or http://www.iamshendy.ca?p=12. This doesn’t fair well for users that want to  access your site directly and can’t remember what “cat” is, or which number “p” was supposed to be set to. More importantly – it prevents search engines from better indexing your content. If a link within your site appears as http://www.iamshendy.ca/fitness/ – a user will have a better chance of remembering it, and a search engine can now index the ‘fitness’ keyword for your site.

With the intro out of the way – here’s a few tips to consider while following through WordPress’ documentation

1. Edit your Permalink Settings by accessing the “Settings” menu, and clicking “Permalinks”
2. Don’t follow the pattern of the “Common Settings” in WordPress’s Permalink Settings
   
   This was the biggest thing that was throwing me off. I had typed in

   http://www.iamshendy.ca/category/postname

   which according to their example – looks like it would work:
   
   But on fact does not – you actually have to use the tags provided.

3. Once you’ve entered your desired custom permalink – you’ll need to update your .htaccess file. This is a file that sits in the same directory as your index.php (usually the root of your site). Create this file, and upload it to your ftp server. Be sure to copy and paste everything that appears in the TextArea after you save:
   

Hope this helps you out – email me if you have any questions.

Shendy.

http://www.bit-101.com/xpath/

Also – I’ve had the good fortune to see Keith speak at FITC the past couple of years. Cool dude.

Shendy.

While the solution provided in the post didn’t help me specifically, it did point me in the right direction.

I also came across another potential solution here.

In addition to the solution provided at Mark Carroll’s blog. I had to republish the site to force a recompile (I would imagine that putting a space in the web.config would have done the same thing).

Thanks to these guys for pointing me in the right direction.

Shendy.

var pinEntrySubmitBtnURL = copyXML.CreateElement(“pinEntry_submitBtn_URL”);
var pinEntrySubmitBtnURLContent = copyXML.CreateTextNode( “<![CDATA[hidden_pin.ashx]]>”);
pinEntrySubmitBtnURL.AppendChild(pinEntrySubmitBtnURLContent);
copyNodes.Add( pinEntrySubmitBtnURL );

All of my intended XML data was coming out as escaped XML:

&lt;![CDATA[hidden_pin.ashx]]&gt;

It took me a few minutes to track this down, but eventually Intellisense gave me the answer. Turns out you need to use the CreateCDataSection function instead:

var pinEntrySubmitBtnURL = copyXML.CreateElement(“pinEntry_submitBtn_URL”);
var pinEntrySubmitBtnURLContent = copyXML.CreateCDataSection( “hidden_pin.ashx”);
pinEntrySubmitBtnURL.AppendChild(pinEntrySubmitBtnURLContent);
copyNodes.Add( pinEntrySubmitBtnURL );

I spent some time searching on the net and couldn’t find any clear examples of this – so hopefully this helps you out.

Shendy.

If you’re running into this problem just make sure the wmode property of your embed is set to "transparent".

With SWFObject:

so.addParam("wmode", "transparent");

Hope that helps,

Shendy.