Someone has found an interesting problem with images in Wordbooker

Apparently Facebook has a maximum size for images and if the images you present to it are bigger than that then it silently fails – no images are processed but no error is produced.

I'm going to look on adding some checks into Wordbooker to make sure that it doesn't pass images that are too big for Facebook.


Posted in Google+, News | Comments Off

Work has been keeping me busy and there have been no real problems reported with…

Work has been keeping me busy and there have been no real problems reported with Wordbooker. So I'm starting to think about what is going to go into the first "Premium" Version of Wordbooker.

When the premium version comes out it does not mean that development on the regular version will stop. I intend to add general functionality to the regular version and over time features from the premium version will filter down into the regular free version.


Posted in Google+, News | Comments Off

Very little to report

Version 2.2.1 came out to fix a couple of bugs and to confirm WordPress 3.8.1 compatibility.  I've found a couple of bits of code that got lost along the line when I was cutting code over from the 2.1.x code base so I'll be putting that back in now I'm not on call at work

Posted in Google+, News | Comments Off

Version 2.2.1

Well the release of 2.2 went a lot better than I expected with more than 7700 people now using the 2.2 release (more than 50% of the total number of users) and there have only been a couple of problems. One of them was down to me being over eager when cutting and pasting and I managed to cut more than I pasted. That was an easy fix – but the other one was much harder to pin down.

Wordbooker 2.2 works fine on 64 bit systems and will work fine on 32 bit systems as long as your Facebook User ID is less than 2147483647 I went round and round in circles on this before noticing one tiny little thing – one single letter!

In the wordbooker_db_functions.php file there is a function wordbooker_set_userdata which writes data into the database. As part of a fix a while back I changed all the code in Wordbooker to pass it through the $wpdb->prepare function. This uses similar syntax to sprintf where you set the format and the variables:

So it looked like this:

 $sql= $wpdb->prepare("INSERT INTO " . WORDBOOKER_USERDATA . 
" (user_ID, onetime_data, facebook_error, secret, 
session_key, uid, expires, access_token, sig,blog_id,facebook_id)
 VALUES (%d,%s,%s,%s,%s,%s,%s,%s,%s,%d,%d)", $user_ID,
 serialize($onetime_data), serialize($facebook_error),
  serialize($secret),  serialize($session->session_key),
 serialize($session->uid), serialize($session->expires), 
serialize($session->access_token), serialize($session->sig), 
$blog_id,$facebook_id);

Its a very simple mistake – and one that only shows up on 32 bit systems with big Facebook IDs :

%d,%d

%d means integer, so the last two fields are loaded as integers. Which is fine on a 64 bit system but on a 32 bit system that last %d means that numbers bigger than 2147483647 get set to that value.

So the fix was simply to change

%d,%d

to

%d,%s

Posted in News | Comments Off

Version 2.2 Finally released

I’ve finally released Version 2.2 to the WordPress Repositories so you should see it wanting up update soon.

The big “headline” feature is the support of custom post types which I covered in a post a long time ago

There are a lot of other changes under the hood – I’ve separated code out to make it more modular and added support for WP_HTTP… in fact WP_HTTP is now the default connection method and only if Curl is available will Wordbooker offer you the opportunity to use it to connect instead.

There’s an updated user manual too which I suggest you read as it hopefully explains the new features and if you have problems then please post a question in the Wordbooker 2.2 Support Forum


Posted in News | 2 Comments

A slight delay in Version 2.2 – nothing major but I didnt't want to push out…

A slight delay in Version 2.2 – nothing major but I didnt't want to push out a version and then immediately have to issue a bug fix release.

Posted in Google+, News | Comments Off

So I’ve implemented the new Like and Send buttons in both versions of Wordbooker…

So I’ve implemented the new Like and Send buttons in both versions of Wordbooker and re-jigged the options page. I still might tweak the Options page in Version 2.2 to make things slightly more obvious as I’d never really liked how I handled the Send options and I’d like to make things better for the new Share options.I’ve also changed the FB API initialisation code from the Javascript SDK initialization to the HTML 5 version, but I’ve checked that it still works if you are using the Javascript version initialization provided by other plugins (i.e. FB API initialization is turned off in Wordbooker).I’m still working out if I can find some way of getting the separate Like and Share Buttons to line up properly if you choose to display them both at the top of the bottom of the post – at the moment it looks like the Share button is aligned at the bottom of the DIV rather than at the top. There probably is an obvious fix for it but I’ve not found it yet.

It now doesn’t look like Wordbooker 2.2 will be out for Thanksgiving because I’m rapidly running out of time.


Posted in Google+, News | 1 Comment

I've been neglecting this page!

Wordbooker 2.2 should be released before Thanksgiving, and the first 2.2 "Premium" Edition should be available soon after Thanksgiving …. it all depends on how much turkey I eat!

Posted in Google+, News | Comments Off

Wordbooker 2.2

I thought it was about time that I posted something about Wordbooker 2.2 as its been a long time coming and there have been rather a lot of beta releases.

It’s taken a lot longer to get it all sorted out because I’ve been keeping both 2.1 and 2.2 running in parallel and I’ve been cross cutting code between the two versions where possible. A lot of work has been done under the covers trying to reduce the number of errors Wordbooker was getting from Facebook by doing more checking for things like expired access tokens before making calls to the Facebook API and the error rates since the last release of Wordbooker have dropped off significantly:

errors

Dropping from 1.4 Million to 265,000 errors with no significant drop in API Calls (the blue line). There are still some odd errors being reported but some of this might be down to people running very old versions of Wordbooker which are just failing continuously because none of the auth processes work any more and some of them I know are old REST API calls which are from Version 1.x of Wordbooker and given that Wordbooker 2.0 was released just over 2 years ago that is pretty damned depressing.

In the midst of all of this I’ve gone through facing redundancy at work which really doesn’t help focus the mind on writing code for fun and lots of other things. But I’ve been working away on the user guide which is pretty much complete and I’ve done a lot of work to hopefully make Wordbooker a lot less “noisy” when it comes to people with different levels of PHP debugging turned on. The language file is stable now so people can work on the POT files for various languages.

So really its all ready to go and I hope to push it out to the WordPress repositories in time for any major issues to have been ironed out in time for Thanksgiving.


Posted in News | 2 Comments

Been doing a lot of work with stupid amounts of PHP error reporting turned  to make…

Been doing a lot of work with stupid amounts of PHP error reporting turned  to make 2.2 pretty much silent for those with PHP error reporting turned on.

Posted in Google+, News | Comments Off

Authentication on 2.1.18 and below.

I’ve just changed the auth process – anyone using 2.1.18 (released 03/09/2012) or below may well find that their sessions won’t revalidate any more.

If this problem affects you then please upgrade to the latest supported version.

There are a lot of reasons for keeping your Wordbooker install up to date such as fixes to get round changes implemented by Facebook as well as internal improvements in the Wordbooker code base.


Posted in News | Comments Off

A good way to get yourself banned

Changing your User Agent and shoving the date and time into it simply makes it more obvious you’re up to no good:

178.43.231.153 - - [24/Jun/2013:10:24:36 +0100] "GET /wp-login.php?action=register HTTP/1.1" 401 348 "-" "Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20100101 Firefox/16.0 2013-06-24 11:23:34"
178.43.231.153 - - [24/Jun/2013:10:41:39 +0100] "GET /wp-login.php?action=register HTTP/1.1" 401 348 "-" "Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20100101 Firefox/16.0 2013-06-24 11:40:35"
178.43.231.153 - - [24/Jun/2013:11:37:50 +0100] "GET /wp-login.php?action=register HTTP/1.1" 401 348 "-" "Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20100101 Firefox/16.0 2013-06-24 12:36:39"
178.43.231.153 - - [24/Jun/2013:12:26:05 +0100] "GET /wp-login.php?action=register HTTP/1.1" 401 348 "-" "Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20100101 Firefox/16.0 2013-06-24 13:24:48"
178.43.231.153 - - [24/Jun/2013:12:50:22 +0100] "GET /wp-login.php?action=register HTTP/1.1" 401 348 "-" "Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20100101 Firefox/16.0 2013-06-24 13:49:03"
178.43.231.153 - - [24/Jun/2013:13:27:20 +0100] "GET /wp-login.php?action=register HTTP/1.1" 401 348 "-" "Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20100101 Firefox/16.0 2013-06-24 14:25:58"
178.43.231.153 - - [24/Jun/2013:14:17:25 +0100] "GET /wp-login.php?action=register HTTP/1.1" 401 348 "-" "Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20100101 Firefox/16.0 2013-06-24 15:15:55"
178.43.231.153 - - [24/Jun/2013:15:49:19 +0100] "GET /wp-login.php?action=register HTTP/1.1" 401 348 "-" "Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20100101 Firefox/16.0 2013-06-24 16:47:16"

Firewalled – along with several IPs from an ISP in Moscow.


Posted in Hints & Tips, News | Tagged , , | Comments Off

You know what I'd really like to be able to do?

Its spend time finishing off Wordbooker 2.2 rather than spending all my time fighting against the never ending deluge of hacking attacks that keep swamping the site.

I had a brain wave on the drive into work this morning so I'm going to look into that when I get home this evening. If it works out then I'll be able to concentrate on finishing off 2.2 and getting it released to the repositories.


Posted in Google+ | Comments Off

Another list of sad people….

These are some of the user accounts people have tried to login to my site as.

Have you really nothing better to do:

5.254.143.40 chattarasee (1 lockout)
5.254.137.147 chattarasee (1 lockout)
5.254.142.105 chattarasee (1 lockout)
88.230.21.133 admin (7 lockouts)
5.254.142.183 chattarasee (1 lockout)
109.194.107.117 admin (1 lockout)
5.254.144.76 chattarasee (1 lockout)
5.249.160.175 tubehuit (1 lockout)
5.254.142.170 Gangbang (1 lockout)
5.254.138.27 salope (1 lockout)
82.222.130.37 admin (1 lockout)
5.249.160.247 salope (1 lockout)
5.254.132.179 salope (1 lockout)
178.137.84.193 Bialleank (1 lockout)
185.5.45.91 tubehuit (1 lockout)
180.183.158.121 jackson hewitt tax advance loans (1 lockout)
198.27.80.111 summpingarylun (1 lockout)
217.131.43.35 admin (2 lockouts)
192.95.38.161 apeteruri (1 lockout)
175.44.15.201 geottomiBen (1 lockout)
50.112.93.204 admin (1 lockout)
192.74.237.184 deEFasptgqb (1 lockout), deEFvdzmdnl (1 lockout)
87.14.89.168 aircrescio@email.it (1 lockout)
78.179.223.198 admin (2 lockouts)
5.254.130.244 Porno (1 lockout), pornopucelle (1 lockout)
5.254.138.204 pornopucelle (1 lockout)
175.44.10.69 Hotvoqks (1 lockout), retromwbzi (1 lockout)
5.254.143.22 pornopucelle (1 lockout)
78.180.128.65 admin (1 lockout)
78.185.63.187 admin (2 lockouts)
88.190.44.218 pissing (1 lockout)
5.254.128.195 Pornoblack (1 lockout)
151.250.117.34 admin (2 lockouts)
5.254.141.248 Sexe gratuit (1 lockout)
5.254.138.202 sadomaso (1 lockout)
5.254.137.217 beurettes (1 lockout)
5.249.161.211 tubesmateur (1 lockout)
188.143.232.224 admin (1 lockout)
78.163.246.138 admin (2 lockouts)
78.187.16.22 admin (2 lockouts)
142.0.137.177 dunsefeslesty (1 lockout)
176.42.156.80 admin (2 lockouts)
176.41.158.94 admin (2 lockouts)
176.41.155.26 admin (2 lockouts)
78.163.209.26 admin (2 lockouts)


Posted in News | Comments Off