mmpresti

I edited the framework/highwind-functions.php file and modified the highwind_move_textarea function, commenting out “print $textarea;” on the last line. Now I only have one textarea.

I tried doing this before by copying the entire “framework” directory to my highwindchild directory, but it looks like that directory has to stay in the parent directory for editing purposes.

Ok, I got it working. I was making things a bit more complicated than they were, as you noticed that it was not necessary to symlink the wordpress directory. When I used to install on apache2 on Debian, I was always under the impression that there had to be a symlink for the install to work. Yet, the wordpress directory could be installed anywhere on the webserver.

This is still a mystery to me: that when I was deploying the site through WebMatrix, with the site installed on a random port number, when opening that random port on my router and verifying that it was open remotely using a web check tool, I was still unable to access the site through my public ip (xx.xx.xx.xx:random port). I made sure everything was ‘open’ on the firewall but when I scanned my ip address with nmap, it was still showing that port closed. Hmmmm….

Thanks for the clarification, ClaytonJames. Solved.

No one has any suggestions. Let me specify: In the wordpress table wp_options I can go ahead and change the ‘site url’ value to ‘localhost’ or my public ip and the ‘home’ value to the same, and when I relaunch the wordpress site the url will be rewritten from say ‘localhost/wp-login.php’ to ‘localhost/wp-login.php?redirect_to=http%3A%2F%2Flocalhost%3A21329%2Fwp-admin%2F&reauth=1 . This will not successfully load the login page.

Only when I specify in the table wp_options that the ‘site url’ and ‘home’ are both http://localhost:21329 do I get a successful login screen when I point my browser to localhost:21329/wp-login.php

Somehow the redirect function in wp-login.php is caching the random port number 21329 and making this a condition of successfully logging in. Where do I change this?

Ok, I figured it out. I was backing up my old wordpress mysql table using mysqldump, and wordpress logs your url at the bottom of each post, with the old ip address. When I restored the old table after reinstalling mysql, the old ip was appended to the posts and many other places in the backup file. This was keeping me from reinstalling wordpress.

Is there anyway around having to reinstall wordpress every time my ip changes?

Wp-cron is definitely not the problem. I set ALTERNATE_WP_CRON to true in wp-config.php, and I’m no longer getting this error message, but I’m still left with the same problem.

Now I’m investigating the first error about replacing mysql-connect() with mysqli or PDO. In doing a little research this seems complicated.

I can’t say I fixed this problem, but it looks far more complicated than I first imagined. When I updated to Trusty (Ubuntu 14.04), the upgrade only partially finished. In other words, I got about 75% through the upgrade because there were unresolvable conflicts. Therefore when I tried to downgrade my version of php I came up against all sorts of unmet dependencies and claims that I had held broken packages. So I couldn’t directly downgrade my version of php.

Instead, I downgraded my version of Ubuntu. Now I’m back on Saucy 13.10 and have an earlier version of wordpress (3.6.1) and an earlier version of php 5.5.3 (the one I was working with before was 5.5.9). There are no problems now and I can download themes and everything appears to be working fine. I may try to update Ubuntu in the future, but I will definitely do a fresh install instead of an update.