I have experience with this issue and find solution maybe work with your problem Check Wp-Content Permission change to 775 Delete or rename your .htaccess like .bkphtaccess Setting permalinks as default and save Turn back permalinks as your custom permalink and save If allowed new .htaccess will create automatic, if not copy text at the … Read more
Here is what I came up with. Seems to be working. If anyone has suggestions for improvement, I’m all ears: // Redirect links to future posts to Coming Soon page. add_action(‘wp’,’redirect_coming_soon_posts’, 0); function redirect_coming_soon_posts(){ global $wpdb; if ($wpdb->last_result[0]->post_status == “future” && $wpdb->last_result[0]->post_date_gmt != ‘0000-00-00 00:00:00’ && ! is_admin() ): session_start(); $_SESSION[‘next_post_id’] = $wpdb->last_result[0]->ID; wp_redirect( ‘/coming-soon’, … Read more
Duh! It was a permissions issue: a folder inside the theme folder (containing all the files triggering the 404 errors) was set to 700 instead of 755.
Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until … Read more
Please try <form method=”post” action=”<?php echo get_template_directory_uri() ?>/abc.php”> I am assuming that abc.php is located in theme folder.
It’s because you have incorrect css being used on some divs within that page. On that page a couple of divs down from the H1 deceleration you have a div with some inline css: <div style=”width: 100%;height: 0;padding-bottom: 56%;position: relative;”> You need to remove the padding-bottom:56%; so it is: <div style=”width: 100%;height: 0;position: relative;”> Then … Read more
I solved this issue by replacing RewriteRule . /index.php [L] with RewriteRule ^(.*)$ /index.php/$1 [L] in .htaccess file.
OK after doing some more research I found out that I had to change the configs for the NGINX files as well. I simply had to add the following parameters before the last closing bracket location /nameofnewsite { try_files $uri $uri/ /nameofnewsite/index.php?$args; } location ~ \.php$ { fastcgi_split_path_info ^(/nameofnewsite)(/.*)$; }
I Found this forum article. It was an issue with the domain mapping and cookies. I ended up making sure the following options were both checked in the Domain Mapping options: Remote Login Redirect administration pages to site’s original domain (remote login disabled if this redirect is disabled)
This was caused by a small bug in my first implementation of the rel=”next” and rel=”prev” features that Google launched 2 weeks ago in my WordPress SEO plugin. That bug has been fixed, you’re up to date and the 404’s should go away soon enough, nothing to worry about!