ProjectArmy

Ok good, this is default behavior not an issue. So now we simply need to update the date to the correct one when you publish posts. We do that with this code, which should be put into your theme’s functions.php file:

function post_published_date( $post )   
{  
    // Apply this to posts only 
    if ($post->post_type == 'post')   
    {  
        // Update the date 
        $pub_post = array(  
            'ID'            => $post->ID,  
            'post_date'     => date("Y-m-d H:i:s"),  
            'post_date_gmt'     => date("Y-m-d H:i:s")  
        );  
      
        // Update database  
        wp_update_post( $pub_post );  
    }  
}  
add_action( 'draft_to_publish', 'post_published_date' );

When you hit Publish, this will automatically update your date. If this solves your issue, don’t forget to mark this topic as resolved. Thanks 🙂

^V

Are you able to edit wp-config.php? If so, when you enabled debugging your debug.log will be created inside /wp-content/ folder.

If you don’t have access to edit wp-config.php, you might need to contact your hosting provider and see if they can help you regain access.

^V

@szoszk you said in your initial post “Although in that case the src of the image is some php file.” Can you share what that URL is and php file? You can remove your domain or replace it with example.com. I’m more curious as to what the URI following your domain name is in this case.

You can enable WordPress debugging and check out debug.log file to see if there are any errors. That’s usually one of the best places to look for errors. More info:
https://codex.wordpress.org/Debugging_in_WordPress

Your hosting error log should be in the “public_html” folder if cPanel hosting, called error_log. But that doesn’t always get populated with errors.

^V

If you click on the empty image inside media library, what URL do you see on the right side?

^V

• This reply was modified 9 years, 1 month ago by ProjectArmy.

It’s hard to say what’s causing an issue. But, we can try to regain access to your admin.

You’ll need access to your FTP/SFTP account. It is also a good idea to create a backup of your website before making any changes just in case. Your hosting panel should have an option to create a backup of all the files and databases.

The first thing you need to do is to disable all your plugins. A plugin conflict or issue can be causing this. When you login to your FTP account, you’ll need to navigate to “wp-content” folder. Inside this folder you will see “plugins” folder. Simply rename “plugins” folder to something else, like “plugins2”. Now, try and see if you can navigate to your WordPress admin via wp-login.php or wp-admin. If you’re able to login, then one of the plugins is causing this issue.

If you still get the same error. The next step is to disable your theme. Inside “wp-content” folder, you will see “themes” folder. Click on it. Inside it, you will see either your theme folder or you might see several different folders for other inactive themes. You need to figure out which folder is your active theme and then rename it, like we did with plugins folder. This will deactivate your theme. After this, try to login again. This should work now.

Start with those 2 steps to regain access to your admin. Let us know what worked.

^V

What error do you see when you try to login at /wp-login.php?

^V

Start with your htaccess file. If you have any custom rules in htaccess file, try removing everything but default WordPress rules.

If that doesn’t work, try resetting your permalinks. Simply go to Settings > Permalinks and click “Save” button. This will reset them.

If that doesn’t work, I would recommend enabling debugging mode and checking debug.log to see what might be causing 500 error with your AMP pages. Usually errors in debug.log will help you identify the issue or another plugin (or theme) that’s conflicting with AMP pages and causing 500 error. More on WordPress debugging is here in the Codex.

^V