I have SQLIImport up and running on a fresh Fuji installation. The warning you have when you regenerate autoloads is because I backported eZPendingActions class from Fuji to be used in previous eZ Publish versions. I'll remove this class in a future version and propose it as a separate download.
Your other errors don't seem to be related to SQLIImport but to other extensions issues. Instead of activating extensions from the admin interface, try to activate manually from your site.ini.append.php file ;)
And by the way, you should take the latest SVN version from trunk (1.2.1) as several issues are fixed in it and I didn't have time to package a new version.
Peder Dukefos
Tuesday 22 March 2011 4:17:00 am
Ah, manually activating from site.ini.append.php worked like a charm!
Thank you :-)
Peder Dukefos
Monday 04 April 2011 1:23:23 am
Hello again,
I've gotten a bit further, but now I've stumbled on another question: How do I send parameters and/or variables into SQLIimport?
E.g. I have a php-file that fetches the nodeID for the object I want to update. And want to send that ID into $content = SQLIContent::fromNodeID($myFetchedNodeID); in my handler.
I've tried adding it through php $_post, $_get and in the call for the handler, i.e. "php extension/sqliimport/bin/php/sqlidoimport.php --source-handlers=myHandler --options="myHandler::myFetchedNodeID=357" "
But, alas to no avail so far. Any tips?
Jérôme Vieilledent
Monday 04 April 2011 2:41:22 am
Hello Peder
Options are passed to your handler's constructor as an SQLIImportHandlerOptions object. This object is iterable and you can access to your options this way :
$myOption = $handlerOptions->optionName; // $handlerOptions is an SQLIImportHandlerOptions object
// Object is iterable
foreach ( $handlerOptions as $optionName => $optionValue )
{
echo "Option name is : $optionName\n";
echo "Option value is : $optionValue";
}
You must be logged in to post messages in this topic!
