thepiweb

Hi @benbodhi,
I am not certain if this will resolve the issue, but you call on functions/enqueue.php
wp_localize_script( 'bodhi_svg_inline', 'ForceInlineSVGActive', $force_inline_svg_active );

and $force_inline_svg_active is as I see is a string (‘true’ or ‘false’)

Maybe turning this into a single array may fix it.

• This reply was modified 3 years, 11 months ago by thepiweb.

Unfortunately our client asked us to remove the specific form from the website.
After the removal the empty records stopped.
If I understand what you are saying let me note that the empty records didn’t seem to be triggered by any form submission.
Personally I didn’t witness, during my tests, any empty record being created during or after a submission of the specific form or any other crm form we use on the site.

Thanks

Hi,

In the createdby of the empty records is recorded the account that is connected with website and the plugin. This account is used only for the connection of the site with the CRM.

Thanks

Hi,

We added a hidden field to the form with a default value and indeed the value is not coming through with these empty records. So it seems these records are not created with the form submission.

Yet, we changed the entity that the form is connected from Leads to a new custom one. The empty fields stopped being created on leads and started appearing to the new entity. It seems that, if not the form itself, the plugin may causing this.

I want to add some more elements that I think will be useful.

• this form is added to all pages on the footer through a wp widget
• Wordpess along with the Crm is connected with an Exchange Mail Server 2016. We have noticed that when the mail server is down these empty fields are created in great numbers. Specifically when it is reported to us that the Exchange Server is down the empty fields are created every minute. Otherwise we see a couple or even only one in a single day.

Thanks again in advance.

• This reply was modified 6 years ago by thepiweb.
• This reply was modified 6 years ago by thepiweb.

Unfortunately setting a custom key attribute on {% form %} did not solve things. The problem begun when in two days about 100 empty records where created on the leads entity from the account that is connected with the website. From then on every once in a while but almost every day 1 to 15 empty fields are created. Some are created in one minute, others between couple of minutes. Yesterday were created 15 and the day before only 1. There are hints, from my point of view, that their creation is triggered from a human factor or maybe a workflow. One reason is that they are created on ‘working hours’. Personally I don’t have access to the CRM workflows. I am only in charge of the plugin and the website implementation of the CRM. I have to exhaust all possibilities that the plugin or the certain form isn’t causing this.

Thanks

• This reply was modified 6 years ago by thepiweb.

Hi @wizardist,

Do you mean I should add a key parameter with a custom value to the {% form %} tag?
For example key=”1234″? Because value=”{{form.key}}” renders successfully a key (of the type 213cgf312gd..) on the front-end.

Hi @wizardist

This is our code

[msdyncrm_twig]
{% form entity="lead" mode="create" language=1032 required=["lastname", "emailaddress1", "firstname"] %}
{% if form.submission and form.status %}
<div class="row">
<div class="col-12">
<div class="alert alert-success">{{ form.parameters.messages.success ?? "Ευχαριστο?με για την εγγραφ? σα? στο Newsletter" }}</div>
</div>
</div>
{% elseif form.submission and (not form.status) %}
<div class="row">
<div class="col-12">
<div class="alert alert-danger">{% if form.parameters.messages.error %}
{{ form.parameters.messages.error }}
{% else %}
{% for descriptor, message in form.errors %}
<div>{{ descriptor }}: {{ message|join(', ') }}</div>
{% endfor %}
{% endif %}

</div>
</div>
</div>
{% endif %}

<form class="form-inline" method="POST" data-toggle="validator">
<fieldset>
<div class="form-group">

<input class="form-control" name="firstname" pattern="^[A-Za-zα-ωΑ-Ω????????????????\s]*$" required="" type="text" placeholder="?νομα:" data-required-error="Το πεδ?ο ε?ναι απαρα?τητο" data-pattern-error="To πεδ?ο δ?χεται μ?νο χαρακτ?ρε? και το κεν?" />
<div class="help-block with-errors"></div>
</div>
<div class="form-group">

<input class="form-control" name="lastname" pattern="^[A-Za-zα-ωΑ-Ω????????????????\s]*$" required="" type="text" placeholder="Επ?θετο:" data-required-error="Το πεδ?ο ε?ναι απαρα?τητο" data-pattern-error="To πεδ?ο δ?χεται μ?νο χαρακτ?ρε? και το κεν?" />
<div class="help-block with-errors"></div>
</div>
<div class="form-group">

<input class="form-control" name="emailaddress1" required="" type="email" placeholder="Email:" data-required-error="Το πεδ?ο ε?ναι απαρα?τητο" data-error="Μη ?γκυρο email" />
<div class="help-block with-errors"></div>
</div>
<button class="btn btn-default" type="submit">Εγγραφ?</button></fieldset>
<input name="_key" type="hidden" value="{{form.key}}" />

</form>{% endform %}
[/msdyncrm_twig]

We use Version 1.2.19 of the plugin and WordPress 5.0.3.

Thanks

Edit: I don’t understand what you mean with ‘ease the requirements’.
We use an input required attribute, a js validation and the fields are required also from the CRM side.

• This reply was modified 6 years, 1 month ago by thepiweb.
• This reply was modified 6 years, 1 month ago by thepiweb.

Thanks @wizardist,

This was very helpful and resolved the issue.
Although I was a little confused with the documentation.
{{form.id}} didn’t return anything and the forms weren’t being submitted.
I used {{form.key}} instead and it worked fine.

Thanks again

Hi @wizardist

We have the newsletter registration on the footer so if we could distinguish the submissions that would be greatly appreciated.

Is there something I can do with the code or should we wait for an update on the plugin?

Thanks

Hi George,

The first form is placed on page content like this:

{% form entity="mds_registrationcontact" mode="create"  %}
    {% if form.submission and form.status %}
    <div class="row">
    <div class="col-12">
    <div class="alert alert-success">{{ form.parameters.messages.success ?? "Ευχαριστο?με για την εγγραφ? σα?" }}</div>
    </div>
    </div>
    {% elseif form.submission and (not form.status) %}
    <div class="row">
    <div class="col-12">
    <div class="alert alert-danger">{% if form.parameters.messages.error %}
    {{ form.parameters.messages.error }}
    {% else %}
    {% for descriptor, message in form.errors %}
    <div>{{ descriptor }}: {{ message|join(', ') }}</div>
    {% endfor %}
    {% endif %}
        
    </div>
    </div>
    </div>
    {% endif %}        
    
    <form  method="POST" data-toggle="validator">
        <fieldset>
        <div class="form-group">
            {% set loc= eventlocations.results.entities[0].mds_location %}
            <input class="form-control" type="text" name="mds_eventlocationtext" value="{{loc}}" readonly />
        </div>
        <div class="form-group">
            <div class="select-wrap" id="mds_eventtitle">
                <select name="mds_eventtitletext">
                    <option value="">-- Seminar Title --</option>
                    {% for eventtitle in eventtitles.results.entities %}
                    <option value="{{eventtitle.mds_title}}">{{eventtitle.mds_title}}</option>
                    {% endfor %}
                </select>
            </div>
        </div>
        <div class="form-group">
            <div class="select-wrap" id="mds_event">
                <select name="mds_eventfulltitletext">
                    <option value="">-- Event --</option>
                    {% for eventfulltitle in eventfulltitles.results.entities if eventfulltitle.mds_location == loc %}
                        <option value="{{eventfulltitle.mds_eventtitle}}" data-sem="{{eventfulltitle.mds_eventtitlelookup}}">{{eventfulltitle.mds_eventdate}}</option>
                    {% endfor %}
                </select>
            </div>
        </div>               
        <div class="form-group">
            <input class="form-control" name="mds_lastname" pattern="^[A-Za-zα-ωΑ-Ω????????????????\\s]*$" required="" type="text" placeholder="?νομα:" data-required-error="Το πεδ?ο ε?ναι απαρα?τητο" data-pattern-error="To πεδ?ο δ?χεται μ?νο χαρακτ?ρε? και το κεν?" />
            <div class="help-block with-errors"></div>
        </div>
        
        <button class="btn btn-default" type="submit">Εγγραφ?</button>
        </fieldset>
    </form> {% endform %}

and the second is placed on the footer with a widget text like this:

<div class="footer-newsletter">[msdyncrm_twig]
{% form entity="lead" mode="create" language=1032 %}
{% if form.submission and form.status %}
<div class="row">
<div class="col-12">
<div class="alert alert-success">{{ form.parameters.messages.success ?? "Ευχαριστο?με για την εγγραφ? σα? στο Newsletter" }}</div>
</div>
</div>
{% elseif form.submission and (not form.status) %}
<div class="row">
<div class="col-12">
<div class="alert alert-danger">{% if form.parameters.messages.error %}
{{ form.parameters.messages.error }}
{% else %}
{% for descriptor, message in form.errors %}
<div>{{ descriptor }}: {{ message|join(', ') }}</div>
{% endfor %}
{% endif %}

</div>
</div>
</div>
{% endif %}

<form class="form-inline" method="POST" data-toggle="validator">
<fieldset>
<div class="form-group">

<input class="form-control" name="firstname" pattern="^[A-Za-zα-ωΑ-Ω????????????????\\s]*$" required="" type="text" placeholder="?νομα:" data-required-error="Το πεδ?ο ε?ναι απαρα?τητο" data-pattern-error="To πεδ?ο δ?χεται μ?νο χαρακτ?ρε? και το κεν?" />
<div class="help-block with-errors"></div>
</div>
<div class="form-group">

<input class="form-control" name="lastname" pattern="^[A-Za-zα-ωΑ-Ω????????????????]*$" required="" type="text" placeholder="Επ?θετο:" data-required-error="Το πεδ?ο ε?ναι απαρα?τητο" data-pattern-error="To πεδ?ο δ?χεται μ?νο χαρακτ?ρε?" />
<div class="help-block with-errors"></div>
</div>
<div class="form-group">

<input class="form-control" name="emailaddress1" required="" type="email" placeholder="Email:" data-required-error="Το πεδ?ο ε?ναι απαρα?τητο" data-error="Μη ?γκυρο email" />
<div class="help-block with-errors"></div>
</div>
<button class="btn btn-default" type="submit">Εγγραφ?</button></fieldset>
</form>{% endform %}
[/msdyncrm_twig]

</div>

On the first one I’ve only included the form code and not the whole twig tag because of the existence of many fetchxml snippets.

Thanks

Hi George,

I see. One way I can think of is using twig to create my own version of the form and fetchxml to populate the available options. Then trying to simulate these behaviors with twig conditionals and/or javascript. Is this one alternative?

May I send an email to your support to discuss these alternatives?

Thanks

I had tried just currentrecord as an object, without the quotation marks, but didn’t and doesn’t seem to work.

Yet `currentrecord.id’ did work. I remembered trying it but it may got in the middle changing quotations off and on.

Thanks again.

Hi again,

I am able to get bounded data with [msdyncrm_twig] using “currentrecord”.
I can’t find the way to use the “record” attribute so I can fill a form’s fields with bounded data as I believe is specified on documentation.
https://docs.alexacrm.com/wpcrm/twig/

record – entity record object to fill form fields from, can be retrieved via currentrecord or entities objects, or a GUID

I am trying using sth like this:

{% form entity="contact" mode="edit" record="currentrecord" name="my contact" %}

{% endform %}

Thanks

Hi,

Yes with twig I was able to get bounded data. Thanks.
Authentication I believe is in the premium package and our client is really reluctant so far to go for.
We are trying to go somewhere in the middle where a user will be able to see a “safe” lets say part of his record and only change certain minor fields.

Thanks again

Hi George,

This certain excerpt from the docs gave me the impression that is manageable:

Parameter name ->
Entity attribute to match the page against. ID is available for every entity. You can create custom key attributes for specific entities (e.g. email, SKU, etc.).

Anyway what I am trying to do is have users being able to access/read their records through the front end. I can’t think of a way using the GUID. If we can’t do it with binding the way I am trying could you suggest how we can do such a thing?

Thanks

• This reply was modified 6 years, 5 months ago by thepiweb.