Hot answers tagged wordpress-version
14
The only reason why the 3.3.3 milestone was marked as completed is because leaving the milestone open interfered with our ticket reports for 3.4.1. (I forgot that milestone closures are reflected in the timeline.)
Generally speaking, we assign tickets to the next minor milestone if they are reporting an immediate regression. So, a regression in 3.2 that ...
12
If you need to get the wordpress version in your script, there is a global variable:
$wp_version (right now it's something like '3.1-RC3-17376')
It contains the wordpress version.
If you need to acquire if from a file, you can read it from /wp-includes/version.php:
function getWPVersion() {
$path = '/path/to/wp-install';
include ...
7
headdesk
Permissions on all WordPress files should be 644. Permissions on all WordPress directories should be 755.
Exceptions:
The uploads directory may need to be 775 or 777, depending on your server configuration.
wp-config.php should be 600, 640, or 644, whatever is the lowest number that works.
Never, ever, give higher permissions than those. ...
6
This is a bit of code I wrote a while back to do WP version detection in the most obvious ways: http://ottodestruct.com/class-wp-detection.phps
There are other methods, more subtle and less obvious. His method is file fingerprinting. Basically checking for whether certain files exist or not.
6
You can hook into style_loader_src and script_loader_src and run remove_query_arg( 'ver', $url ) on the URL:
<?php
/* Plugin Name: Remove version parameter for scripts and styles */
add_filter( 'style_loader_src', 't5_remove_version' );
add_filter( 'script_loader_src', 't5_remove_version' );
function t5_remove_version( $url )
{
return ...
4
You can hook on option_update_core and edit the update url, as a plugin you can do something like this (Remember to disable the plugin after updating wordpress)
add_filter('option_update_core','wpse_26750');
add_filter('transient_update_core','wpse_26750');
function wpse_26750($options){
global $wp_version;
$updates=array(
...
4
To always get latest plugin take for example my plugin:
http://wordpress.org/extend/plugins/wordpress-file-monitor-plus/
the download link for the latest is:
http://downloads.wordpress.org/plugin/wordpress-file-monitor-plus.1.1.zip
but if you remove the version from the download link you always get the latest version:
...
4
Check your folder permission. Most likely your folder doesn't have correct permission.
The permission should be set to 777. If you have cPanel on your host, then it would be easy for your to do because the GUI is similar to WIndows.
4
You can also just go to http://site.url/readme.html in a web browser. The readme file ships with every version of WordPress and displays the installed version number prominently at the top of the page.
Also, if you can view your site's front-end (I know you said you can't access the dashboard, so I'm just assuming your blog is public), you can "view ...
4
see:
http://clark-technet.com/2010/12/wordpress-self-hosted-plugin-update-api
Basically the idea is to hook your update checking function to the pre_set_site_transient_update_themes filter. The version array key you return from this function will be compared by WP to the current theme version from style.css....
Use the admin_notices action to make your ...
4
Stable release of WP is the one meant for production. Any serious issues (such as security) are addressed via minor releases. Some of the fixes for not that serious issues can be received ahead of schedule with Hotfix plugin.
Non-stable versions are usually run by WordPress developers for the sake of experimentation and early access to new features. That is ...
4
Usually a plugin developed in WordPress version will run fine on several newer versions. What you need to care about is 'deprecated` features/apis in WordPress. Any API in WordPress is not removed overnight, rather it remains deprecated for several versions. You will get such a list here:
http://codex.wordpress.org/Category:Deprecated_Functions
When you ...
4
This is explained in the core ticket #12554.
Change label in UI for Post Thumbnail and Page Image to "Featured Image" for both
We should change the UI label for the post thumbnail box on post and page editor screens. It's post thumbnail for posts, and page image for pages, but it's not always a thumbnail and the labeling is inconsistent. Let's call ...
3
Imo it's your server or your host. Hosts that are known for not really caring about security on their shared services are dh and mt (and some others out of the big players). Both had been successfully attacked and infected multiple times last year. As i use one of those myself (contract running) and had the same problem as you (different installs, no ...
3
Even when Wordpress is running version 3.1, sites are still being defaced.
Even? There had been one major and five security releases since that version. If you are implying that 3.1 should be reasonably secure - it is not.
but the only answer seems to be outdated Wordpress sites
What had you done to exclude themes, plugins and hosting used to jump ...
3
There's a page in the Codex that shows exactly that:
WordPress > About » Statistics
But really, it all depends on what features you're using. A safe bet for a new plugin would be to support WordPress 3.1.X and above (since that's the current stable release). You're setting yourself up for a lot of hurt if you try to do too much backwards ...
3
You can...
Load the file into the file where you want to display the 'hey username' message:
<?php include(TEMPLATEPATH .'/check-user-hello.php'); ?>
.
Then in that file "check-user-hello.php"
You need to put this code
<?php
if ( is_user_logged_in() ) {
global $current_user;
get_currentuserinfo();
echo 'Hey ' . $current_user->display_name;
...
3
I just want to add the batch version of this script, as I've spent quite a bit of time till I found this:
Use it to print all the versions of all your wordpress install within a folder.
find . -name 'version.php' -path '*wp-includes/*' -print -exec grep '$wp_version =' {} \; -exec echo '' \;
3
Well, it seems like the answer is "No, there's isn't an existing solution for this."
If anyone wanted to write one, these might be helpful:
The general process described in the question
http://wordpress.org/extend/plugins/deprecation-checker/
http://wordpress.org/extend/plugins/log-deprecated-notices/
http://adambrown.info/p/wp_hooks/hook
...
3
I just found a solution as an automated service over at http://de.wpseek.com/pluginfilecheck/
It's does exactly, what was asked for including the generation of list of used functions and giving a suggestion for the Plugin-Header comments.
3
If you're manually installing a plugin, you need to disable and delete the old version. However, WordPress does allow you to update your plugin programatically.
If your plugin is hosted on the WordPress.org repository, it will prompt the users to install updates for you. You've likely seen this with Akismet and other plugins already.
If your plugin isn't ...
3
You can always use GitHub. WordPress has an official (view-only) GitHub repository, and GitHub has an excellent comparison feature.
Here's the GitHub comparison of WordPress 3.4.2 vs 3.5.
3
Note: there is no Version "3.04". There is a Version "3.0.4", though.
The important thing to understand with WordPress version numbers is that, unlike many software applications, the latest major version is not Version X, but rather, Version X.Y. So, in WordPress, Version X.0 is no more important, stable, or secure than Version X.1 (and in fact, generally ...
2
I would only increase the version number if users needed to download the plugin again. The "Tested up to" variable is not used when the plugin is installed, only when people want to install it or want to upgrade. In that case, the information comes from the server anyway, so you don't need to force a new download of your plugin.
Of course, if your ...
2
I'm just assuming here but this is usually done by fingerprinting for specific version files/directory's/code and sometimes even size.
For example you can remove all the meta versions tags ( isn't there like 12 places) and .txt file for 3.1 but since 3.1 is the only version to include the following new file by default, it is rather easy to fingerprint.
...
2
For me, "Featured Image" was still missing from the Screen Options tab, even after clearing the cache and restarting the browser. In my case the problem was related to having a WordPress 3.2 Multisite install. With this setup, the Media upload buttons must be checked in Network Admin to enable the featured image meta box in the editor (these are unchecked by ...
2
Yes. First of all, to be able to highlight the current sorting method, we attempt to retrieve if the GET variable sort_by occurs in the url:
<?php switch ($_GET["sort_by"]) {
case 'most_recent':
$active = 'most_recent';
break;
case 'most_favourite':
$active = 'most_favourite';
break;
case 'most_viewed':
...
2
Holy schmoly shadowpress - what a risky idea.
I imagine one could write a cron plugin to do it, BUT what a risk....Already the auto wordpress multi update feature makes it way too tempting to just hit the update button on a bunch of updates in one go.
Recommended 'safe' procedure for system upgrades is something along the lines of:
1) read the ...
2
Many of the serious vulnerabilities in WP lately are actually in the plugins. I recently found a combination of plugins that, when installed together, caused WP to accept ANYTHING as a password. As long as an attacker knew a valid administrative login (hello, Admin!) on a site running those plugins they could do anything.
In addition to that some sites ...
2
that could be caused by post revision being saved, and you should use wp_insert_post_data anytime you want to do something before the post is saved, here is an example plugin i just cooked up to test it and it looks like this:
<?php
/*
Plugin Name: wpse37901
Plugin URI: http://en.bainternet.info
Description: answer to ...
Only top voted, non community-wiki answers of a minimum length are eligible
