plainblack.com
Username Password
search
Bookmark and Share
View All Tickets
Can't call method "getValue"  (#2386)
Issue

Update: Changed the Severity to Critical as it's impossible now to publish any new content. Am I the only one who's getting this problem ?  

After upgrading to 7.0, I get this errors in the webgui.log:

2006/07/06 17:53:13 - ERROR - WebGUI-imt_ilance_nl.conf - Log::Log4perl::Logger::__ANON__[41] - Caught exception executing workflow activity pbwfactivity0000000006 for instance 8IWxlMbSaQsvsi_orPDVow which reported Can't call method "getValue" on an undefined value at /zut/domains/shared_webgui6/WebGUI/lib/WebGUI/Asset/Post.pm line 293.

Also, spectre is complaining about this:

Can't use an undefined value as an ARRAY reference at ../lib/Spectre/Workflow.pm line 195.

All commits get the status "Pending".

"showRunningWorkflows" shows this error:

Commit Without Approval2006-06-15 12:33:39error / 2006-07-06 17:54:38

Len Kranendonk, www.primaat.com

---- Are you a chess player ? Challenge me for a game ---

Solution Summary
Comments
martink
0
7/7/2006 6:19 am

Ok I figured out what went wrong here.

Len's site had some version tags containing thread assets that were committed (so they were in the pending version tags list). The parent asset (a collab system) of these Thread assets, however, was under a versiontag that had not been committed yet.

Therefore the Thread assets could not instanciate their parent. They need to be able to do this or else they will bork.

I fixed the problem by committing the tag containg the parent asset, and manually setting the priority of the corresponding workflow instance to 1 in order to make sure the parent was coimmitted before the threads.

This is of course still a bug.

I'm not sure if it has anything to do with this bug, but the collabsystem is a child a page which is on the clipboard.

martink
0
7/7/2006 9:23 am
The ARRAY ref error has its own thread: https://www.plainblack.com/bugs/tracker/spectre-tries-to-delete-the-same-workflow-instance-twice#w0b6jRHtV9sqlQBqK9abNw
JT
0
7/19/2006 2:14 pm
I don't remember which version, but I fixed it so that you can't post to a collaboration system that is new and hasn't been committed. So this bug was fixed. I'll deal with the arrayref bug on that
erik.svanberg
0
11/1/2006 10:09 am

I just experienced the very same bug when deploying a package (including a collaboration with one thread). To get around this I manually deleted the thread asset in the database and the workflow was successful.

WebGUI version 7.0.9 

/Erik 

JT
0
11/7/2006 12:14 pm
Yeah, I found a flaw in my original logic for this fix. I've changed that logic since in 7.1 and it's now working. The only case where this will not work, and I'm not sure how to get around it is if somehow a CS post gets committed and the CS itself never gets committed.
Details
Ticket Status Closed  
Rating0.0 
Submitted Bylen 
Date Submitted2006-07-06 
Assigned To unassigned  
Date Assigned2012-05-16 
Assigned By 
Severity Critical (mostly not working)  
What's the bug in?  
WebGUI / WRE Version 7.0  
URLbugs/tracker/can39t-call-method-quotgetvaluequot
Keywords
Ticket History
© 2012 Plain Black Corporation | All Rights Reserved