Post - Create
Create a new WordPress Post using SQL Server
- See SQLHTTP easy setup for WordPress
- See API Call documentation for parameter values and other information
- Create the stored procedure documented below
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 |
CREATE PROCEDURE usp_WordPress_v2_Post_Create( @Profile nvarchar(100), @slug varchar(100) = NULL, @status varchar(10) = NULL, @password varchar(50) = NULL, @title varchar(100) = NULL, @content varchar(MAX) = NULL, @date varchar(50) = NULL, @date_gmt varchar(50) = NULL, @author int = NULL, @excerpt varchar(50) = NULL, @featured_media int = NULL, @comment_status varchar(10) = NULL, @ping_status varchar(10) = NULL, @format varchar(10) = NULL, @meta varchar(MAX) = NULL, @sticky varchar(5) = NULL, @template varchar(MAX) = NULL, @categories varchar(100) = NULL, @tags varchar(100) = NULL, @liveblog_likes int = NULL, @Response nvarchar(MAX) OUTPUT, @StatusCode int OUTPUT, @StatusDescription nvarchar(MAX) OUTPUT) AS DECLARE @URL nvarchar(MAX) DECLARE @QueryString nvarchar(MAX) DECLARE @HTTPSessionID uniqueidentifier SET @URL = SQLHTTP.net.AuthParam(@Profile, 'RootURL') EXEC SQLHTTP.net.UrlBuilder @URL OUTPUT, @Profile, 'wp-json', 'wp', 'v2', 'posts' EXEC SQLHTTP.net.QueryStringBuilder @QueryString OUTPUT, @Profile, 'slug', @slug, 'status', @status, 'password', @password, 'title', @title, 'content', @content, 'date', @date, 'date_gmt', @date_gmt, 'author', @author, 'excerpt', @excerpt, 'featured_media', @featured_media, 'comment_status', @comment_status, 'ping_status', @ping_status, 'format', @format, 'meta', @meta, 'sticky', @sticky, 'template', @template, 'categories', @categories, 'tags', @tags, 'liveblog_likes', @liveblog_likes SET @URL = @URL + @QueryString EXEC SQLHTTP.net.HTTPSession @HTTPSessionID OUTPUT EXEC usp_WordPress_v2_Auth_Header @HTTPSessionID, @Profile, @URL, 'POST' EXEC SQLHTTP.net.HTTPRequest @HttpSessionID, @URL = @URL, @Method = 'POST', @ContentType = 'application/json', @Accept = 'application/json', @StatusCode = @StatusCode OUTPUT, @StatusDescription = @StatusDescription OUTPUT, @Response = @Response OUTPUT GO |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 |
DECLARE @Response nvarchar(MAX) DECLARE @StatusCode int DECLARE @StatusDescription nvarchar(MAX) EXEC usp_WordPress_v2_Post_Create @Profile = 'My Website', @Title = 'Test Post', @Slug = 'test-post', @Status = 'draft', @Content = 'This is a test post', @Response = @Response OUTPUT, @StatusCode = @StatusCode OUTPUT, @StatusDescription = @StatusDescription OUTPUT IF @StatusCode >= 400 EXEC SQLHTTP.net.RaiseHttpError @StatusCode, @StatusDescription, @Response ELSE BEGIN DECLARE @X xml SET @X = SQLHTTP.net.Json_To_Xml(@Response, '0') --The XPath syntax below was easily generated by executing the following commands: --EXEC SQLHTTP.net.XQueryHelper @X --and then executing: --EXEC SQLHTTP.net.XQueryHelper @X, 'JsonObject' SELECT T.C.value(N'@id', N'nvarchar(MAX)') AS [id] ,T.C.value(N'@slug', N'nvarchar(MAX)') AS [slug] ,T.C.value(N'@status', N'nvarchar(MAX)') AS [status] ,T.C.value(N'@date', N'nvarchar(MAX)') AS [date] ,T.C.value(N'content[1]/@raw', N'nvarchar(MAX)') AS [content_raw] FROM @X.nodes(N'/JsonObject') T(C) END |
1 2 3 4 5 |
id slug status date content_raw ----- ---------- -------- -------------------- --------------------- 68 test-post draft 2017-08-14T10:38:58 This is a test post |
- Categories – Fetch
- Category – Create
- Category – Delete
- Category – Fetch
- Category – Update
- Comment – Create
- Comment – Delete
- Comment – Fetch
- Comment – Update
- Comments – Fetch
- Media – Delete
- Media – Download
- Media – Fetch
- Media – Update
- Media – Upload
- Media Item – Fetch
- Page – Create
- Page – Delete
- Page – Fetch
- Page – Update
- Pages – Fetch
- Post – Create
- Post – Delete
- Post – Fetch
- Post – Update
- Post Type – Fetch
- Posts – Fetch
- Settings – Update
- Status – Fetch
- Statuses – Fetch
- Tag – Create
- Tag – Delete
- Tag – Fetch
- Tag – Update
- Tags – Fetch
- Taxonomies – Fetch
- Taxonomy – Fetch
- Types – Fetch
- User – Create
- User – Delete
- User – Fetch
- User – Update
- Users – Fetch
IMPORTANT DISCLAIMER
CODE/SQL ON THESE PAGES ARE PROVIDED AS-IS AND ARE AVAILABLE FOR ILLUSTRATIVE PURPOSES ONLY.
USERS ARE REQUIRED TO ABIDE BY THE TERMS AND CONDITIONS FOR USING REFERENCED THIRD PARTY WEBSITES AND/OR APIs FROM THEIR RESPECTIVE WEBSITES. WE DO NOT CONDONE ANY VIOLATION OF THIRD PARTY WEBSITES AND/OR APIs TERMS AND CONDITIONS USING OUR SOFTWARE.
USERS SHALL BE SOLELY RESPONSIBLE AND BE SOLELY LIABLE FOR VIOLATION OF ANY RULES SPECIFIED BY THIRD PARTIES FOR USING THEIR WEBSITES AND/OR APIs, OR INFRINGEMENT OF RIGHTS OF SUCH THIRD PARTIES.