• Resolved TRILOS

    (@trilos)


    EMEFS Version 1.0.15

    After insertion in form.php:

    		<div class="input">
    			<label for="xyz"><?php _e('Contact E-mail','emefs'); ?
    
    ></label><br />
    			<?php EMEFS::attribute('xyz'); ?>
    			<?php EMEFS::error('xyz'); ?>
    		</div>

    a php notice appears in output while WP debug mode is active:

    Notice: Undefined index: xyz in (…)/httpdocs/wp-content/plugins/events-made-easy-frontend-submit/emefs.php on line 554

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter TRILOS

    (@trilos)

    …and there′s no output of #_ATT{xyz} in the Events Made Easy Plugin′s event detail page.

    I like to have a seperate contact email value in the form to be shown in the output. Would EME′s Custom attributes help for this purpose and how would I use them in EMEFS?

    Plugin Author Franky

    (@liedekef)

    You can’t use EMEFS::error for custom attributes ??
    But I fixed the code so that even that index warning won’t pop up anymore.
    For the second part: the attribute needs to be “used” somewhere first in the EME settings (or in a defined EME template, even if unused for that event), then your event will show it when editing.

    • This reply was modified 8 years, 1 month ago by Franky.
    Thread Starter TRILOS

    (@trilos)

    OK, plugins updated, EMEFS′ form.php addition changed to

    <div class="input">
    	<label for="orgamail"><?php _e('Orga E-mail','emefs'); ?></label><br />
    	<?php EMEFS::attribute('orgamail'); ?>
    </div>

    and added in EME′s event detail format:
    <p>Orgamail: #_ATT('orgamail') </p>

    When opening admin.php?page=events-manager now, your ui-dialog appears: “Error when connecting to the server” (“Fehler”, “Bei der Verbindung mit dem Server ist ein Fehler aufgetreten.”) …

    Plugin Author Franky

    (@liedekef)

    Error connecting to the server is not an EME issue ??
    Check your webserver or any other thing that might block your access …

    Thread Starter TRILOS

    (@trilos)

    Sorry for bothering and posting my suspicion too rash – this error was so extraordinary and appeared very short after editing form.php. The error does not occur now.

    Wondering if I get your right that EMEFS::attribute(‘orgamail’) should “initiate” this extra attribute “orgamail”. But I created an event with EMEFS and EME does not show this value while editing the event, even not after publishing the event.
    And as mentioned above, I′ve added this in EME′s event detail format:
    <p>Orgamail: #_ATT('orgamail') </p>
    But the event detail page does not parse this, it only displays this original line.

    Maybe I′ve missed some little logic or syntax detail…

    • This reply was modified 8 years, 1 month ago by TRILOS.
    Plugin Author Franky

    (@liedekef)

    I just noticed the syntax you use for your attributes … it’s the old deprecated (and now removed) syntax, so that’s why it is not showing.
    Use #_ATT{orgamail}, see also https://www.e-dynamics.be/wordpress/category/documentation/8-custom-attributes/

    Thread Starter TRILOS

    (@trilos)

    Thanks for this hint on EME. (May be I copied this old code from an example in one of the support forums here or on e-dynamics.be.)
    The placeholder is not displayed any more, but the value does not appear.
    So we′re back on the EMEFS question, see the form.php addition as described earlier in this thread: Is this code all we need to get the value (for “orgamail”) submitted by the form?
    I still not see this new field or value when editing admin.php?page=events-manager&eme_admin_action=edit_event&event_id=nnn or on the event detail page.

    Plugin Author Franky

    (@liedekef)

    Hmmmm … wait, you said “event detail format”, correct? Do you mean just “Details”? Because the details is not really a format setting …
    Let me explain the history:
    – normally attributes can only be set in the EME settings pages, in the “format” parts
    – I extended it to also check all defined templates for used attributes (in the past)
    – the last version also checks for “format” settings in the own event (but that doesn’t make much sense), but not the “details” part (since the details is also part of the format).

    So, I suggest you create a dummy template with just all the attributes you want to use (you don’t even need to use that template in your events).
    I’m thinking about redoing the attributes, making it more like “form fields”, but that’s for the future …

    Thread Starter TRILOS

    (@trilos)

    resolved

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘extra attribute, php “Notice: Undefined index”’ is closed to new replies.