I have an event listener on elements.onPopulateElement, what I want is make a last minute decision if I want to populate or not. I have certain customfields on an admin CP user (eg company). All entries (in this case in the section "normalUsers", these are entries not actual users) have that same field company (companiesDropdown). I can detect in the code below that the entries' companiesDropdown field does not match the currentUsers companyDropdown field. But how can I tell the calling piece of code not the populate this element?

The following code it initialised in the plugin init method

private function _initEventPopulateNormalUser() {
    craft()->on('elements.onPopulateElement', function(Event $event) {
        // HERE we check if we actually save a normalUser section entry, may be a bit brute force, we will polish that later
        $lCompanyIdEntry = $event->params['element']->getAttributes(array('sectionId'));
        if (! isset($lCompanyIdEntry['sectionId'])) return;
        if ($lCompanyIdEntry['sectionId'] != $this->mNormalUsersSection) return;

        $lCurrentUser = craft()->userSession->getUser();
        $lCompanyIdUser = $lCurrentUser->companiesDropdown[0]->id;

        $lEntryCompanyId = $event->params['element']->companiesDropdown->first()->id;

        if ($lCompanyIdUser != $lEntryCompanyId) {
                Somewhere here I want the element to be emptied and
                all functionality calling it, like a elementindex template,
                to not show the element in its listing

private function _getNormalUserSection()
    if (is_null($this->mNormalUsersSection)) {
        $lSection = craft()->sections->getSectionByHandle('normalUsers');
        $this->mNormalUsersSection = $lSection->id;

I am not really clear on what you are trying to do. My guess is you are trying to add your own validation to saving an element and trying to block that with your own custom checking of content values etc?

I don't think listening to the event will help as you cannot send a message to say this element is not valid from an event listener - the event does pass you a element that is about to be saved but you cant return the modified element from the listener.

What I would suggest is building a custom fieldType that contains some validation rules that peeks in at the content of other fields.

class My_CustomFieldType extends BaseFieldType

 All the normal filetype stuff like name etc here.

public function validate($value)
  $errors = parent::validate($value);

  if (!is_array($errors))
    $errors = array();

  // DO you logic here to test then set an $variable to true or false
  // if your conditions are met then add to the $errors array below if there is a problem.
  // if you want to access other field in this element do this:
  //   $owner     = $this->element;
  //   $fieldData = $owner->getContent()->getAttribute(array('sectionId'));

  if ($variable){
    $errors[] = Craft::t('You are not allowed to edit this element.');

  if ($errors)
    return $errors;
    return true;


Im thinking that this will be able to stop the entry being saved. Hopefully thats what you were looking for.

  • Not really trying to stop an element from beeing saved, I'd like to stop it from getting populated. Eg. I have an internal authorisation subsystem certain users of certain companies are not allowed to see certain entries not beloning to their companies. I'll give it a try using a custom field type. Thanks for the extensive answer.
    – pythic
    Aug 7 '14 at 20:56
  • When you say that you don't want the entry being populated are you saying that you still want the entry to be saved but remove data from some fields before saving? Aug 7 '14 at 23:17
  • Luke, no I do not want the entry saved. I just want the out of the box entrylist overview (the menu item "Enrties" not to show certain rows based on x
    – pythic
    Aug 8 '14 at 8:38
  • Oh, there is no way of doing that with events or hooks as far as I know. Aug 8 '14 at 15:52
  • Populating does not mean listing though. So I think the your using the word populating incorrectly in this instance. The craft onelementpopulation refers to when an element is instantiating with all it's data as an object. Aug 8 '14 at 15:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.