Wednesday 16 November 2011 5:05:11 pm
We are currently trying out your extension and have come across a little problem. Here's our setup.
We have several developers who check out the project (Community Project 2011.8) from our subversion server.
All developers have Apache on their local machines and are developing on this.
All developers share the same database and var/-directories (except cache).
All developers commits their code to a Subversion-server, which is then automatically deployed to our test-server.
Here is the problem, your extension only works on the developers machines, not on the test-server. We've added a few debug-writes to mobilebrowserdetecttype.php and it is showing fine on the developer machines, but not on the test-server.
The developers machines are Ubuntu with PHP 5.3.6 on Apache 2.2.20.
The test-server is running CentOS 5.5 with PHP 5.3.8 on Apache 2.2.3
I cannot understand why it won't work on the test-server as it is the same code, the same database and the same var/-dir.
Any help would be much appreciated.
Thursday 17 November 2011 1:35:12 am
I think you might want to check your siteaccess and override (global) ini settings.
If the settings expected by the extension/workflow event are not properly assigned and available when the workflow event is triggered, it does nothing at all by default.
Which seems to match the use case you described.
Just read the rather simplistic and basic PHP involved here in the workflow event in question (it's dead simple to understand), http://svn.projects.ez.no/mobileb...erdetect/mobilebrowserdetecttype.php
From what I could tell reading the extension, it has no code which differentiates between one host and another (at all), let alone any code that tells the difference between servers it runs on.
Alternatively you should also consider debugging the workflow event PHP execution (add a die before the return in the execute method, and use php debugging skills to test line by line where your error is occurring). I do this all the time and it's a brease to solve problems like this ...
I hope this helps ...
Wednesday 23 November 2011 12:05:15 am
Thanks for your reply.
I don't believe this is a ini-issue as it is working on another server with the exact same ini-files.
As I said, all code is identical on the servers. The only thing that differs is the behaviour
Thanks any way.