Hammer02
Forum Replies Created
-
Well no help from the community, but through trial and error I fixed the problem.
I replaced the absolute file directory in index.php with default wildcards
I replaced the absolute file directory in wp-config with default wildcards
define(‘ABSPATH’, dirname(__FILE__) . ‘/’);
And everything is working.
Forum: Themes and Templates
In reply to: Theme twenty twelve 1.6 sidebar is being pushed downWPYogi
Thank you. I found the offending orphan </div> in sidebar.php and I took it out. Problem solved. I have no idea how that extra tag got there. Must have been added during the upgrade to Twenty Twelve 1.6.
Thank you for your help.
Forum: Themes and Templates
In reply to: Theme twenty twelve 1.6 sidebar is being pushed downThank you WPyogi,
That wrapper with the extra closing tag is generated by the theme. Where do I go to correct that? I can’t seem to find that code in the editors but I may be looking in the wrong place.
Thanks.
Forum: Themes and Templates
In reply to: Theme twenty twelve 1.6 sidebar is being pushed downNo one has any ideas? Is no one else using theme twenty twelve?
It took a long time, but I finally have my automatic upgrades working again running WP 4.0 on a Windows Server with IIS6.
The WP 4.0 wp-config.php file contained a line that read:
define( ‘WP_TEMP_DIR’, ABSPATH . ‘wp-content/’ );
I changed it to the following to actually tell wp the temp file name:
define( ‘WP_TEMP_DIR’, ABSPATH . ‘wp-content/tmp’ );
This then gave me a new error further along in the plugin automatic update process. The error said WP could not delete old files. So I changed the permissions of the IIS Windows iusr_computername by adding special permission of delete files.
That did it. Automatic updates for plugin are working again for WordPress 4.0 on a Windows Server 2003 running IIS6.
Hope this helps the next person.
Spent another four hours today searching for a solution to the problem caused when I upgrade to WP 4.0 when I lost auto upgrade ability. Still getting the followin error:
Downloading update from https://downloads.wp.xz.cn/plugin/broken-link-checker.1.9.5.zip…
Download failed. Destination directory for file streaming does not exist or is not writable.
Nothing I try seems to be working.
One note I did not mention before is I have three other WP blogs on the same server that I have not upgraded to 4.0, and they are working fine. I can use all the auto upgrade functions in the older versions of WordPress so this problem is isolated to my install of WordPress 4.0.
So the question remains. What happened to automatic upgrades when I updated to WP 4.0.
Nothing I change in file permissions seems to have any effect at all on the problem.
Any suggestions for next steps would be appreciated.
Hi Puravida
I sent you an email … did we open up a ticket? I have not heard back yet.
Thank you for the reply.
When I tried to view the WP-Portfolio Error Logs, I get the following returned error:
The filename, directory name, or volume label syntax is incorrect.
Does that give any suggestion of where the problem may be?
I should note that I did a manual upgrade to WP 4.0, in case that may give a clue of where the breakdown is occurring.
Still can’t get Ftp to work within WordPress on a windows server. I was hoping that someone in the word press world could offer some direction on why I am having this problem? Surely other users must have had this problem before?
Forum: Localhost Installs
In reply to: Can't view newor old pages after upgrade to WP 4.0.Hi Laura,
Thanks for the link to thread on permalinks. You should note the pretty permalinks are working fine for the blog posts. It is the link to the pages that I am having the problem with. So I don’t have any evidence that this is a permalink problem by itself.
I am trying to learn what wp file contains the page link information. My theory is that this file was not updated or the settings were lost when I upgrade the installation to WP 4.0. So far I have not been able to learn how the page link information gets updated in the database.
Forum: Localhost Installs
In reply to: Can't view newor old pages after upgrade to WP 4.0.Hi Laura,
I am not sure about web.config I just did a search of my wordpress installation and can’t find that file. Do you know where it is supposed to be?
I do have a wp_config that has all the database information in it.
Should there also be a web.config file?
Remember, the blogs post are appearing correctly. It is the pages that I am getting the 404 not found error.
Just an update on the problem. After a few more hours and manually changing permissions in IIS 6, I am now receiving a different error message. My interpretation is that the ftp connection is now established, but the plugin upgrade still can not create a directory of write.
Update Plugin
Downloading update from https://downloads.wp.xz.cn/plugin/google-sitemap-generator.4.0.7.1.zip…Unpacking the update…
Could not create directory.
I see threads on this issue throughout the forum, but they are older and offer no fixes for WP 4.0. The important thing here is that prior to upgrading to 4.0 I was able to install and upgrade plugin from the WP dashboard. Now I can not.
Hopefully someone involved in the release of 4.0 can offer some advice.
Thanks.
Forum: Localhost Installs
In reply to: Can't Select DatabaseI uninstalled 3.3.1 and installed 3.2 and everything works fine.
Forum: Fixing WordPress
In reply to: screen option not functioning — can't edit/postI am trying a brand new install, including a new database. Now I am getting this error message when I run install.php
—————————————–
Can’t select databaseWe were able to connect to the database server (which means your username and password is okay) but not able to select the Lobstercoast database.
Are you sure it exists?
Does the user root have permission to use the Lobstercoast database?
On some systems the name of your database is prefixed with your username, so it would be like username_Lobstercoast. Could that be the problem?—————————-
Are you familiar with that error message?
Forum: Localhost Installs
In reply to: Trouble connecting to databaseI had a similar problem with windows server 2003. I had to uninstall Tcp/Ip 6 before it would connect. It was not enough to just de-select it. I had to uninstall it.