![\"Pixie](\"http:\/\/blog.jedbrubaker.com\/wp-content\/uploads\/2008\/09\/pixie_logo_large.png\" "\\"Pixie"){kind=logo}
It looks like it is a Pixie CMS weekend. The following error was giving me some trouble, so hopefully throwing this out into the blogosphere will save someone some time.<\/p>\nIt looks like it is a Pixie CMS weekend. The following error was giving me some trouble, so hopefully throwing this out into the blogosphere will save someone some time.<\/p>\n
Problem:<\/strong> When updating a static page’s content you get one of several validation errors.<\/p>\n Solution:<\/strong><\/p>\n It is that simple, but if you would like more of a description, read on. 1 – create new page “press” **at first i thought it was the “edit this page” link from the webpage however, there are additional conditions…<\/p>\n 1 – create new page “linktest” ” maxlength=”12″ \/><\/p>\n 12 – view page = content displays\/functions correctly Troubleshooting the problem<\/strong><\/p>\n \nOn line 1024 of lib_core.php, you can uncomment<\/p>\n \nI would then see output like the following when trying to save a page:<\/p>\n Notice the strange content in page_parent, privs, page_views, etc. <\/p>\n This record is in the pixie_core database table, and is created when you first setup the page. The problem problem isn’t with “editing”. The fields aren’t validating because the record of the page itself is screwed up.<\/p>\n Why did this happen? page_description isn’t getting cleaned correctly in the SQL insert statement. I haven’t had a chance to dig into that one yet. Fortunately the work around outline above works just as well.<\/p>\n Thanks to Kathryn for providing creating the condition and chatting with me on our bug-hunt.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":" It looks like it is a Pixie CMS weekend. The following error was giving me some trouble, so hopefully throwing this out into the blogosphere will save someone some time. Problem: When updating a static page’s content you get one of several validation errors. Privs is a required field Publish is a required field and […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[6],"tags":[],"class_list":["post-241","post","type-post","status-publish","format-standard","hentry","category-technology"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pJP4m-3T","_links":{"self":[{"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/posts\/241","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/comments?post=241"}],"version-history":[{"count":0,"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/posts\/241\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/media?parent=241"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/categories?post=241"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/tags?post=241"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\n
\n
\n
\nRecreating the problem<\/strong><\/p>\n\n
\n2 – from pixie publish, add content “test one test two”
\n3 – update = success
\n4 – view page = content displays correctly
\n5 – click “edit this page”
\n6 – add content “test three”
\n7 – click update = success
\n8 – view page = content displays correctly
\n9 – click “edit this page”
\n10 – add content “| test four|”
\n11 – click update = “Privs is a required field”
\n12 – view page = content displays correctly
\n13 – click “edit this page”
\n14 – content displayed on webpage does not appear in the edit “press”
\npage; only “test one test two test three” appears
\n15 – add content again “| test four|”
\n16 – click update = “Publish is a required field”<\/p>\n
\nitself that was causing the problem. but now it appears to be
\ninserting a “|” in my content that does it.<\/p>\n
\n2 – from pixie publish, add content and link “test link one”
\n3 – update = success
\n4 – view page = content displays\/functions correctly
\n5 – click “edit this page”
\n6 – add content and link “test link two”
\n7 – click update = success
\n8 – view page = content displays\/functions correctly
\n9 – click “edit this page”
\n10 – add content “| test link three |”
\n11 – click update = “Saved updates to the linktest page” **however,
\nthe “| test link three |” doesn’t physically appear in the edit
\ncontent window and below the content window the following text appears:
\ntest link three<\/p>\n
\n13 – click “edit this page”
\n14 – same content and random text from step 11 appears.\n<\/p>\n<\/blockquote>\necho $sql; \/\/view the SQL for current form save<\/code><\/p>\n
\n`page_type` = 'static',`page_name` = 'about',`page_display_name` = 'about',`page_description` = '
\nabout gallery
\n',`page_blocks` = 'google_analytics',`page_content` = '
\ncontact info
\n',`page_views` = ' location and hours ',`page_parent` = ' ',`privs` = '7',`publish` = '',`public` = '2',`in_navigation` = 'yes',`page_order` = '0',`searchable` = 'yes',`last_modified` = '20080907145610'
\n<\/code><\/p>\n