Josh

Have you tried to turn on error reporting; and see if any errors or warnings are being generated?

[moderator note; relates to this thread]

Well.. I seriously doubt the default functionality of wp_insert_post() would return an existing ID. The ID column is set to auto-increment… so any newly created table entry would be given a new auto-incremented ID (meaning it would never be “recycled”).

It’s hard to say for sure without seeing your external PHP script; but it sounds like you may be adding a post ID in your wp_insert_post() array (from your external PHP script).

Here is an excerpt from the WordPress Codex Page on wp_insert_post():

IMPORTANT: Setting a value for $post[‘ID’] WILL NOT create a post with that ID number. Setting this value will cause the function to update the post with that ID number with the other values specified in $post. In short, to insert a new post, $post[‘ID’] must be blank or not set at all.

So, perhaps somewhere in your external PHP script it is pulling an ID from an existing entry before running the wp_insert_post() function.

It is definitely beneficial to minimize the number of http requests being sent. Many people put all of their site images on a single image file (using Photoshop or some other photo editing software). Then, there is only one http request for all images on the site (referred to as “CSS Sprites”).

In this case; I would probably reduce the http requests and go with the single file. Even though it is slightly larger in size; I think reducing two http requests is better.

You can always optimize the “combined” image, for the web. If you go to a site like GTMetrix; and read through the stats, you’ll see links where you can get an optimized image of all images on your site (with file sizes; and how much space can be saved).

Hi,

I would suggest becoming intimately familiar with the codex page on Moving WordPress. Pretty much everything you need to know regarding moving WordPress is on that page.

Now, in order to get back into your site to begin moving it the proper way; you’ll need to change those “site url” and “home url” values back to how you had them set originally. In the codex page link above; you’ll read about a few different methods for manually changing those values.

Let us know if you get stuck along the way.

Well.. a few things to consider here.

Who exactly are you wanting to prevent from editing pages? WordPress uses Roles and Capabilities to allow different users different permissions.

From the list in the link; you can see that the “edit_pages” permission is shared by super admin, admin and editor. This means if the user is an author, contributor or subscriber; they cannot edit posts or pages. You could just assign the author role to the users you don’t wish to allow to edit posts or pages.

There are certainly other solutions; but this one is easiest to implement.

Hi,

It appears your website has a redirect loop.

I would begin by deactivating all plugins. If you can login to your admin panel; deactivate ALL plugins from there. Then, manually clear your browser cache.

Also, I would switch to the default 2015 theme.

Now, logout… and see if your front-end website loads.