ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

$this->form_validation->run() issues

August 13, 2012 4:55pm

Subscribe [1]
  • #1 / Aug 13, 2012 4:55pm

    pohadmin

    3 posts

    Hi.

    I’m having some trouble when updating a channel entry for a client’s site. Specifically, I’m receiving the following error.

    Fatal error: require_once(): Failed opening required 'Zend/Registry.php' (include_path='.:/usr/share…admin/expressionengine/third_party/url/library/') in /var/...expressionengine/third_party/url/library/Zend/Validate/Abstract.php on line 381

    This error is presenting itself from this block of code in /admin/expressionengine/controllers/cp/content_publish.php around line 200

    if ($this->form_validation->run() === TRUE)
    {
    
     if ($this->_save($channel_id, $entry_id) === TRUE)
     {
      // under normal circumstances _save will redirect
      // if we get here, a hook triggered end_script
    
      return;
     } 
     // used in _setup_layout_styles
     // @todo handle generic api errors
     $this->errors = $this->api_channel_entries->errors; 
    }

    Also, not sure how relevant this is, but I have the following plugins enabled for this channel:
    - Entry Access (http://cl.ly/3v3X1H3R222N)
    - Better Workflow (http://cl.ly/1n0T1k46211M)

    Last, it is worth mentioning that these entries are coming from a Cron job pulling from a third-party. The data (in the database) looks identical to channel entries that are working, but there seems to be the occasional hiccup with these channel entries.

    Any help would be greatly appreciated.

  • #2 / Aug 14, 2012 5:22pm

    Kevin Smith

    4784 posts

    Hi pohadmin,

    It looks like that error is actually the result of a third-party add-on that’s in the third-party folder under expressionengine/third_party/url. I’d recommend checking with the maker of that add-on to see what’s going wrong here.

  • #3 / Aug 15, 2012 4:39pm

    pohadmin

    3 posts

    Kevin,

    In hindsight, that makes perfect sense. For some reason (perhaps it was that 2:30 feeling), I was under the impression that the URL field type was part of the core. My mistake. It turns out their was a glitch in the validate() function. Returning true ultimately fixed the issue (even it makes the validation somewhat irrelevant).

  • #4 / Aug 16, 2012 1:54pm

    Kevin Smith

    4784 posts

    Awesome, glad to see you were able to track down the issue with them. Let us know if we can help again in the future!

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases