ronald.fuquay

Thank you for the reply, I have enabled php error loging and display_errors to on.

However, I had a bigger issue yesterday that lead me to re-install my local dev site. I used 4.3 as the base install, reinstalled my database and files and have yet to see the error show its face. I think the fresh install fixed whatever was the issue.

<strike>Oh and to add to my previous statement, the only thing the white screen affects is the backend. The front end of the dev site still is view-able if I had it open in another screen, I can refresh page and its just fine while the back-end is white screened</strike>

Well navigating to another page brings up a white screen so never mind.

Ok so what happens is when I hit update on a post/page the entire browser screen goes white. there is no content/navigation/dashboard to be seen. Refreshing the page does not help, it remains blank/white.

When I hit the browser’s back-key (previous page) I get back to the pre-updated post or page edit screen, but it appears that nothing was done. If I then click on “All Posts/Pages” and navigate to the one I was editing and click on it, all of the edits I was doing when I hit update went through.

So it seems that the edits do get saved, its just that the redirect/refresh after hitting update causes a white screen until you hit the back key.

Does that help?

At first glance it seems like the correct code, its just that he forgoes the $labels array and defines the labels in his $args array instead.

And of course it seems to have fewer arguments but im guessing you really only need to have those arguments if you plan to change something from the default setting.

Am I correct in my assumption?

And I have screenshot examples of the error, but I cannot seem to upload them to my post