Rules Integration

patchy patch patch

Let me know if you would rather this be a seperate module. I figure browscap is small enough that this additional functionality wouldn't be too much of a burden.

Jumped the gun... Forgot to add the getter callback to the other properties.

and now status

Una Mas.

I found out that the "boolean" values stored in the array were actually text. This was unexpected... but I did make adjustments. In addition... I removed a debug watchdog that was in my last patches.

So in my case I need to keep certain browsers from hitting a specific page using backed code. Specifically I want search engines to be able to index some pages while other browsers hit a squeeze page. The reasoning for this is partly because of the functionality of the squeeze page relies on cookies but I also have to run a rule that sets a flag if I decided to let someone through.

With that said this achieves something that JavaScript is better at but let's me also perform the same tasks when JavaScript is not an option via rules as opposed to a custom module.

I realized I didn't answer your second question. As for scalability... I wish I didn't have to do the giant array. If there was some functionality in the existing module that determined the interface of the information... I wouldn't have to do it that way. Ideally there would be something somewhere defining all the properties a browser could have and the descriptions.this would allow the flexibility the ini file has and fulfil the needs for other information gathering hooks. As for performance... seems to be negligible in difference.

it's working on a production server for me with this patch. I use it to allow search bots through but redirect other people through a squeeze page on http://oakmotors.com/inventory

As far as I know... this choke page that I created is the only way for a user to get to a page. If the user has not went through the choke page, then it hasn't been stored in their session that this has happened and any inventory page they go to will take them back to the choke page. This isn't a javascript side solution, otherwise, the bot wouldn't care because it doesn't parse Javascript anyway.

So basically if I didn't have a rule that said, "Hey I'm a search engine bot, don't make me go to the choke page" then the search engine bot would be 301ed back to the choke page for any links to any inventory or lists of inventory, making the inventory not indexable by the search engine... make sense?

I'll take a look at the patch.