hapzfl

The problem definitely has to do with permalink settings because some stuff I can get to work with one setting and other stuff with another on localhost. Only on the remote server everything works.

The problem I am trying to resolve:

On localhost the image has a href=https://localhost/2012/12/21/page_name/dsc123456 this is NOT working, i.e this reference is not found.
However, the src=https://localhost/wp-content/uploads/…. is working

On the remote server
href=https://site.com/wordpress/2012/12/21/page_name/dsc123456/ this is working.

Obviously replacing “site.com/wordpress” with localhost in the database does not do the trick as all the href references containing ../page_name/… are invalid on localhost. The physical path does not exist.

nice idea but no, there were no // to replace

No, that’s not it, unfortunately. I wish it were, although than the question would be: how come?

If you compare the localhost code with that on the remote server the statements are exactly the same aside from the URL. That’s what’s so puzzling: how can the same code produce different results?

The localhost html page code is stored in the MySQL database and was converted from the original using Wordepress procedures.

Thank you, thank you, thank you!!! It worked!!!

open up your search option on your Win 8 OS and just plunk in php.ini

That new Win8 search function worked beautifully and showed me immediately the php.ini file in C:\Program Files (x86)\IIS Express\PHP\v5.3\php.ini.

Yesterday I was not looking into the(x86)folder not being aware that IIS Express might be in both. Why they installed a x86 and a 64bit version and than run the x86 one is a mystery but might have been caused by the WordPress installation?

Similarly there is a PHP v5.3 and a v5.4 installed but the v5.3 is used.

In any case, ClaytonJames you saved my day. And hopefully somebody else’s too.

Yes,I am running Win8Pro.

It’s been a while since I messed with…

(cue the music from the movie “Jaws”) …WebMatrix

Well, XAMPP didn’t but WeMatrix2 did work. What can I say.

Unfortunately, C:\Program Files\IIS Express\.. does not contain a PHP folder. And a php.ini file is only where I put it.
And I put my localhost on a separate partition and folder. In that folder I put my php.ini file.

Did you restart the server so that the changes you made to the .ini file take effect? ??

Yes, many times. I.e. after every change; although some posters mentioned that this should not be necessary.

Thanks for all your help!

“located inside of the directory where you installed php”

Which php? There are tons of them in a number of directories. Maybe my ini file is in the wrong one. As I mentioned and suggested elsewhere, I put php.ini first in the wp-admin folder. As that did not work, I moved it to the root folder where wp-activate.php, wp-config.php, etc. are.

I had problems with getting XAMPP and phpAdmin to get access to MySQL running under Win8. phpAdmin just gave me an error message related to PW failure. And believe me, my PW was correct. Probably another php file with the wrong settings but none of the suggested solutions made a difference. Strangely enough, when I installed WordPress a couple of years ago under Vista I encountered no problems. I never did it under Win7.

In any case, I uninstalled XAMP and installed WebMatrix. And I have been able to install and run WordPress from there.

Maybe there is a misunderstanding.

“edit the limitations directly in the php.ini file on the server”

My PC is my server = localhost.

Thanks for your prompt reply. I was partially successful after uninstalling the stand alone version of MySQL. At least I was able to
access the database via phpAdmin; but WordPress still would not run.

I finally gave up and uninstalled everything associated with XAMP.That was necessary tosucceed with the next step:

Downloading and installing the MS Web Platform Installer. Using the MS Web Matrix I now have WordPress running successfully and locally under Win8.

Following up on a post elsewhere, installing the plugin Google Libraries did the trick. Now everything seems to work normal again.

dale_c, thanks for the hint, IT WORKED !

I have tried it with IE9, Firefox 8, and Chrome: always the same unpleasant result.

yes, I have; and I created another thread on this issue

No changes were made. I published and it happened.

I deactivated all plug-ins. That was a tricky issue, however. Everything looked screwed up after de-activation and I thoght I lost everything until I realized that the information just scrolled out of the usual visible area all the way down. So I was able to activate my plug-ins again.

What do I use:
Theme: Calotropis

Plug-ins:
Categories to Tags Converter Importer
CKEditor for WordPress
Hotfix
NextGEN Gallery
NextGEN Resize
TinyMCE Advanced
WordPress Importer
WP Google Fonts

I am using Calotropis. Switching to Twenty Eleven or Twenty Ten did not resolve the edit problem.

I installed the hotfix: that did not resolve the edit problem either.