i got everything running now i have the issue that .css and .js files are used with /index.html at the end of the link
aws is autmatically adding /index.html to every file and block the frrontend from loading
is there any fit to this?
Thanks!
]]>The homepage is showing an error while all the other pages are working fine. When I try to get to the homepage, It either shows 404 or redirects me to this site==>https://www.domain.com. I tried to access the WordPress admin but the site is not showing.. It is showing a basic site with no content==>https://magicpoint.ae/index.html/.
I think the homepage got replaced with this new theme. I don’t have much knowledge in coding or programming. Please help as you can and let me know if you need any further information.
Any help is appreciated.
Thank you.
I’ve been reading the other topics with the same name to help solve this issue and they haven’t done anything yet. This was the solution that fixed some sites (updating the area in bold text).
# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
<strong>RewriteRule . //index.php [L]</strong>
</IfModule>
# END WordPress
I recently started working with this client and they have already installed the theme to their hosting platform so I think during this process they accidentally installed it with /index.php
I’d like to remove this /index.php because it’s displaying a strange cover page.
Let advise me what you think this causing this issue.
If you click on any of the pages you’ll see the coming soon page I’ve set up to hide her new website that’s getting ready to launch. I’d like this to be shown when clients go to her URL, not after clicking through.
]]>Negotiation: discovered file(s) matching request: /mysite/index.html (None could be negotiated)
it is indeed correct. HOWEVER, whyever is there any attempt to open index.html???
1) I have disabled plugins and found that they are not the cause.
2) I see the error messages in the log when I supply the url https://mysite.com and https://mysite.com/index.php
3) The messages appear when I connect to the site from various browsers on different platforms.
I don’t know if this is a browser issue, a wordpress configuration issue or what.
Any suggestions?
]]>After recent updates, I noticed that all links have this “folder/index.html” at the end, and I wonder how could this affect page ranking when moving from dynamic to static and vice versa…
I just reverted part of the site to dynamic (leaving most other parts as static) and noticed that google had indexed the reverted pages with the explicit “folder/index.html” at the end, and when clicking on them they appear as 404 as WP just references to “folder/”; and I believe this would also be the case with potential in-links from other websites.
I think before this plugin added the links as “folder/” to allow for seamless transition from dynamic to static and back, without any change on structure/links.
Is that possible to generate the static version with “folder/” references on the links?
Thanks again for making such a useful plugin, where in your page can one send a donation?, I could not find it.
]]>But I’m wondering about any tips for seeing what I’m doing while developing the WordPress site? I would have probably installed WordPress in a subdirectory for easier development, but someone else set it up in root and it would be too much trouble to change this now.
For instance, I’m playing around in the theme Customizer, but the interface is showing me the index.html page, NOT the WordPress home page that I’m trying to customize. I know with other pages I can possibly get by with the ‘Preview’ option, but how do I see what I’m doing with the Home page in the Customizer?
– Any other tips for being able to see what I’m doing on the WordPress site without affecting the static index.html site?
I know there are ‘coming soon’ types of plugins that help with this too, but then I’d have to redesign the static page in the plugin’s interface. Would rather not.
THANKS
]]>What file(s) in WP have this .html information? Where/how can I update them so the site will be secure according to Google?
]]>I’ve set coming soon page in .html and WordPress shop is available after logging to WP. I’ve some problems with Stripe – it cannot access https://home.com/?wc-api=wc_str url so payment on my testing environment won’t work.
Do you have some suggestions what can I do to have index.html and stripe working together? If I remove index.html it all works.
Regards,
Marta
Fatal error: Uncaught Error: Call to undefined function wp_die() in /srv/users/serverpilot/apps/main-site-duckonwater/public/wp-content/advanced-cache.php:167 Stack trace: #0 /srv/users/serverpilot/apps/main-site-duckonwater/public/wp-content/advanced-cache.php(9): _ce_file_path() #1 /srv/users/serverpilot/apps/main-site-duckonwater/public/wp-settings.php(84): include('/srv/users/serv...') #2 /srv/users/serverpilot/apps/main-site-duckonwater/public/wp-config.php(40): require_once('/srv/users/serv...') #3 /srv/users/serverpilot/apps/main-site-duckonwater/public/wp-load.php(37): require_once('/srv/users/serv...') #4 /srv/users/serverpilot/apps/main-site-duckonwater/public/wp-blog-header.php(13): require_once('/srv/users/serv...') #5 /srv/users/serverpilot/apps/main-site-duckonwater/public/index.php(17): require('/srv/users/serv...') #6 {main} thrown in /srv/users/serverpilot/apps/main-site-duckonwater/public/wp-content/advanced-cache.php on line 167
The only way to resolve is to remove the plugin. The site now redirects /index.html to the home address as it should.
Has anyone else experienced this? I only discovered this when index.html started to come up in Google searches! Maybe worth checking your websites.
Hope there is a fix soon as this is by far the best cache plugin about for WP!
]]>