The impact for me and others which makes it impossible for us to upgrade to 3.2 in the near future are
. convincing host providers to upgrade PHP & MySQL – mine waht’s to charge! so the alternative is to move but not until the contract runs out.
. convincing plugin authors to upgrade their code – or hacking the code ourselves if the author can’t be found/motivated.
. convincing theme authors to upgrade their code – ditto to above.
. Educating the editors, authors and contributors of our sites to navigate the new admin panels (they are not very computer literate).
. Finding time to fully test and implement the upgrade.
I do really think this should have been a major release number not a dot release.
]]>I’ve just noticed that on version 3.0.3, if I hover over the Page 2 link in the Posts page to get to the second page of posts, this is the link it sends me to and it works just fine: (https://www.in.gov/visitindiana/outdoorsblog/blog/wp-admin/edit.php?paged=2 )
On version 3.1, 3.1.1 and 3.1.2, here is the link it sends me to (and it then kicks me out to re-login:
(https://192.1.1.1/visitindiana/outdoorsblog/blog/wp-admin/edit.php?paged=2)
I’m wondering if the 3.1 and beyond versions could be keying off the host or server ip parameters in the HTTP header. Since this comes through via the IN.gov proxy servers, they see my server as 192.1.1.1.
Did WordPress change it to pull the host name instead of a static entry in 3.1 and higher versions? If so, is there any way for me to fix this? The site itself runs just fine for consumers, but on my back end, I have to re-login every time I page through posts, pages, comments, users (or do a search within wp-admin for any of those things either).
Can anyone help?
]]>I suppose it could be a theme or plugin issue, but I would think there would be an error message and either way I don’t know what to do next.
]]>define('CONCATENATE_SCRIPTS', false );
option mentioned in the MasterList and nothing.
In TinyMCE screen, the Visual screen shows only the HTML buttons. If you click HTML, the screen literally shows HTML source with no buttons. Not sure why this is happening but it has put a major crimp on my posting. Please take a look. Thanks!
]]>The Permalink settings page indicates “Permalink structure updated.”
Then I use the sidebar widget to go to https://www.jbizchicago.com/category/blog/ and I am redirected to the home page. But if I use the default settings I can go to https://www.jbizchicago.com/?cat=310
When did this occur:
The problem started after I upgraded to 3.i
What I have tried:
I tried using the 2010 theme
I tried changing permissions on the .HTaccess file
I tried deactivating wpcache.
What does the .htaccess file look like?
After changing the settings to a custom structure the code looks like this
code
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
Options -Indexescode
Any help would be appreciated.
I unlike a lot of people am still having issues with the wp 3.1 permalinks.
Background:
I heard from users that categories ( the_category() in the loop ), post linking ( the_permalink() in the loop ) from index and categories sidebar ( using wp_list_categories() ) bring up 404 pages. I am using the custom permalink structure of /%category%/%postname%/ (which i thought was the most popular way, and featured on the wp help page).
What I have done so far:
– Started off by doing a clean install (new db, new folder on my dev server). Downloaded wp 3.1 and installed it in the new folder via my FTP client. Did the normal setup that i do all the time (100s of times before). Things were functioning from a wordpress standpoint except for the stated issues above (category and post pages getting 404s).
– So since it was a clean install there were no plugins that might be causing the permalink issues. But i went ahead and deleted the two default ones that come with WP 3.1 just to make sure (even though they were still disabled). Still getting 404s.
– So then i proceeded to do the suggested .htaccess delete and respawn action. Did this as described by many sites and still had the same issue. I did this like 10 times.
– So i was starting to think it was my theme… So i turned off my theme and reverted to the default (twenty10 theme). Keeping my permalinks set to /%category%/%postname%/. The same issue was happening with this theme. So this is what made me think that it was not my theme and more of a WordPress 3.1 issue.
– If i set my permalinks back to default, they of course work fine, but i have thousands of people using my theme and use the custom permalink structure. So I am afraid that those people are a.) going to have broken sites if they upgrade and b.) have broken links if they revert to the default permalink structure.
– I tried to install the hotfix plugin and that did nothing.
– I made sure that my code was not chaining permalinks like some of the plugins that were causing the issues. Nothing there to cause my troubles…
The only other step that i have not done was install another instance of wp 3.1 in a completely different folder on my server… I was saving this as a last effort if there wasnt a fix that someone uncovered.
So that is where i am and what i have done. Hope that this is clear and links you to a possible solution.
Regards
-estern23
]]>Also there are two links visible on top –> All, Active and no Inactive link is visible as well!
Ability to Network Activate also seems to have disappeared!
Add New Plugins is missing as well!
]]>Image uploads (slowly), and displays in the media window.
But size shows “(0 × 0)” and if I try to use Edit Image button I can’t edit the image but instead get this message:
"Image data does not exist. Please re-upload the image."
I have 2 different WP installs each with unique plugins, and the problem exists on both installs.
Is it WP 3.1 recent upgrade? Is it a plugin? Other?
]]>Warning: reset() expects parameter 1 to be array, null given in [...] /query.php on line 2890
Anyone having the same problem? Any fixes? Does anyone know if the free version of WPML is still under development?
On the WPML website they talked about this issue, stating that they fixed it for the commercial version (29$ – 79$) 2.1.1
Thanx
fred