andy brudtkuhl

"that's the most annoying thing. one one hand you have an excellent open source product and on the other you have enterprisey sales and plans" - andy brudtkuhl

"@mark_ellul thanks for pointing that out! :) But yes - I agree.. I think since their support costs are so high they should at least provide a trimmed down open source version" - andy brudtkuhl

"Which variable?" - andy brudtkuhl

"I'm not familiar with that plugin specifically (although it looks awesome and I may need it on a project soon) but after reading the docs briefly you should just be able to add the translations in via the Custom Fields array in the library." - andy brudtkuhl

"Yea you can store them in a dictionary if needed. I actually first built this library to move a ton of hierarchical content from a legacy CMS to WP. I ended up building a recursive function that handled it nicely. My recursive function had a parameter called parentId that defaults to 0 (if you set it to 0 WordPress knows it's a top level page). So the function just set it every time and would pass the parent id in from the parent page as it recursed. Worked well." - andy brudtkuhl

"Yea I saw that - https://twitter.com/abrudtkuhl... I watched one of their pre-launch webinars on it and they kind of hid pricing til the end when questions were asked. Essentially you will need to pay for one of their support levels (which I think start at 5 figures a year) to get access to Shield." - andy brudtkuhl

"You would set the ParentId property on the child page var parentPage = new Post { PostType = "page", Title = "The Parent Page", Content = "content", PublishDate = DateTime.Now, Status = "publish" }; var parentId = client.NewPost(parentPage); var childPage = new Post { PostType = "page", Title = "The Child Page", Content = "content", PublishDate = DateTime.Now, Status = "publish", ParentId = parentId; }; var childId = client.NewPost(childPage);" - andy brudtkuhl

"It's not a method - it's a property on the client. You can always set it to another var if it's out of scope where you need it. It's the BaseUrl property you set on the client so the library knows where the WordPress site you are using is located. https://gist.github.com/abrudt..." - andy brudtkuhl

"client.NewPost will return the WordPress Post Id So you can use that ID to build the permalink without making another XML-RPC Call. Ex: var id = client.NewPost(post); var permalink = String.Format("{0}/?p={1}", client.BaseUrl, id); // permalink = http://brudtkuhl.com/?p=234 If you have pretty permalinks setup in your admin then it will redirect to it." - andy brudtkuhl

"Is it from the difference in your publish date between app and Wordpress server? I haven't seen this issue otherwise" - andy brudtkuhl

"thanks for checking it out! Andy Brudtkuhl @abrudtkuhl <http: twitter.com="" abrudtkuhl="">" - andy brudtkuhl

"Your welcome! Got an update to fix a couple issues coming this week" - andy brudtkuhl

"Thanks for coming back and posting your solution! I have a similar feature I'm working on this week and this is sure to help" - andy brudtkuhl