Hi Sebastian Are you using eZ publish 3.0 or 3.1? The multiplexer was not ready for use in 3.0 and we have therefore no way of doing this. The multiplexer was finished for 3.1 and should work for what you are requesting. What is the error message you get?
Jo Henrik Endrerud | System Developer @ Seeds Consulting | http://www.seeds.no
Im using version 3.1-1 Revision: 2703. The error I get is:
Fatal error: Call to a member function on a non-object in /var/antenna/www/irc/public_html/kernel/classes/workflowtypes/event/ezmultiplexer/ezmultiplexertype.php on line 177 Fatal error: eZ publish did not finish it's request
Thanks for your help.
Certified eZ publish developer with over 9 years of eZ publish experience. Available for challenging eZ publish projects as a technical consultant, project manager, trouble shooter or strategic advisor.
This is strange. I can't reproduce this error here. The error message you are refering to describes that the event can't information about the current node, but that doesn't make sense... Are you having many muliplexer in a row in your event? If so, can you try to make a new workflow with only one multiplexer and se if you get the same error? What settings have you set on the multiplexer?
Jo Henrik Endrerud | System Developer @ Seeds Consulting | http://www.seeds.no
Hi, I have a single multiplexer. i tried a couple of combinations and currently I have:
sections: any
classes: any
users without workflow ids: none workflow to run: Other workflow that runs successfully standalone, but not in combination with multiplexer.
I wondered if my data caused the error so i emptied ez_approve table, workflow tables and notification tables. Multiplex still did not work.
Kind regards, Sebastiaan
Certified eZ publish developer with over 9 years of eZ publish experience. Available for challenging eZ publish projects as a technical consultant, project manager, trouble shooter or strategic advisor.
This is very strange. Does this error happen on every node, or just on some classes? Does this also happen for all users (try to log in as admin and check if it happen here as well)?
Jo Henrik Endrerud | System Developer @ Seeds Consulting | http://www.seeds.no
Another way to do it, is to put couple of approval events one after another in one workflow, after that you can set up each of them for different editors and sections, for example first one is for section 1 and editor is user_1 for second you set up section 2 and user 2, the only problem in this case is that setting should not intersect.....
