jbusci

I just solved this problem for myself. are you using

query_posts();

?

Cause if you are, you need to realize that you are altering the main loop and have reset the global query.

here is my code example

global $wp_query;
	query_posts(array_merge(array(
	     'category_name' => 'news-events',
	     'orderby' => 'date',
	     'order' => 'DESC',
	     'posts_per_page' => 5
	     ),$wp_query->query));

yeah, just ignore all that stuff, your local environment is safe.

but you do want to create a user like I explained above. Also, google is your friend. You will be able to get answers cause what you are doing now has been done and blogged about to death for a decade or more ??

have fun!

the

::1 is IPv6 route. i think windows just sticks that in there to be cute.

your localhost was resolving to that route, which would be fine if you wanted to configure your apache server to resolve an IPv6 address.

But uhh.. by the time we get around to caring about IPv6 locally, you’ll be an expert at some technology that hasn’t been invented yet heh

Good luck, I am leaving the support page.

Don’t worry about messing up. The beauty of running locally is that if things get too bad, you can just delete everything and start over.

i develop professionally so I see all sorts of configurations to be honest.

you should be able to install a wordpress supported FTP server if you have a shell access. Not sure about vsftpd being supported by wordpress tho.

so DHCP is disable on the interface that you are reporting as your internal IP address.

Is that the interface that your webserver is running on?

Your webservers internal IP address should not be forwarding you to your router/modems internal IP address (default gateway)

what happens when you type in 192.168.254.254 in your browser?

do you get the same results as typing in 192.168.254.14?

so your host is using vsftpd? cause thats probably not supported in wordpress. you can always copy up the folders with an ftp client that does support secure ftp servers.

I found it to be a PITA myself, eventually wp may get around to supporting file transport security.

look at this

127.0.0.1 localhost
::1 localhost

127.0.0.1 localhost

make it be just

127.0.0.1 localhost

lol ooops

resolved

So wordpress was indeed functioning as it should. apparently my RewriteCond was too verbose and wordpress rescued me by gracefully serving up the closest match it could find for the index.html I was calling.

Here is the working rewrite rule. of course substitute https://www.domain.com

RewriteCond %{THE_REQUEST} ^([^/]+/)*index\.html\ HTTP/
RewriteCond %{THE_REQUEST} ^.*/index\.html
RewriteRule ^(([^/]+/)*)index.html$ https://www.domain.com/$1 [R=301,L]

well, this isn’t really to customize a page. We already answered that question.

I was just trying to give you a way to play around locally so you didn’t have to mess up your live site.

and yes, if you want a great site, you either have to pay someone or learn this stuff for DIY.

So you need to go to
C:\Windows\System32\drivers\etc\hosts

and edit that file.

but..

it is tricky to edit.

here are the instructions for editing that file.

https://helpdeskgeek.com/windows-7/windows-7-hosts-file/

once you know how to edit it correctly,

just get rid of comment syntax in front of

#127.0.0.1 localhost

so it should be

127.0.0.1 localhost

is your host using sFTP? cause I still think there is a tracker issue for this for future release. not sure what version you are on, but as recent as a year ago wordpress did not support sFTP.

hmmm…

post the whole ipconfig /all command here please

you might need to do that too.

The file is placed at : C:\Windows\System32\drivers\etc\hosts

by default windows ships with :

# localhost name resolution is handled within DNS itself.
#   127.0.0.1       localhost
#   ::1             localhost

You have to un-comment the mapping for localhost:

# localhost name resolution is handled within DNS itself.
127.0.0.1       localhost
#   ::1         localhost

Note: you will not be able to edit the hosts file as its a read-only file. To edit, you have to be the administrator, copy the file to some other location, edit it and then copy it back to the etc directory.