Viewing 15 replies - 1 through 15 (of 19 total)
  • Plugin Author e_durose

    (@e_durose)

    Hi @amunalaima,

    When does this error occur?

    On activation?
    When saving API values?
    When mapping a form?
    When submitting a mapped form?

    I could not recreate the error on my side.

    Also, I made a couple of updates to the plugin’s html encoding and re-uploaded it to the directory.

    Thread Starter amunalaima

    (@amunalaima)

    It occurs when clicking the “map fields” tab. instead of displaying the page or the contents of page, the whole screen looks like the screenshot. Ok, ill try reinstalling and see if that works.

    Thread Starter amunalaima

    (@amunalaima)

    hi! Unfortunately i still can’t use the plugin. Whenever i click “field mapping” tab it gives me the error:

    This page contains the following errors:

    error on line 10 at column 41: Entity ‘lsaquo’ not defined
    Below is a rendering of the page up to the first error.

    I can’t map any fields at all, and can only use old version which doesn’t tag things correctly because the “Question” doesn’t transfer over to OAP. It just disappears somewhere…

    Plugin Author e_durose

    (@e_durose)

    Hi @amunalaima,

    I looked at the source code for my development environment and that character “lsaquo” is in the title html. It is the < sign and is a character that WordPress core inserts into the title for all of my plugins it seems.

    Please see screenshot.
    https://dev.danddcompany.com/wp-content/uploads/2013/05/screen_shot_040313.png

    I don’t know why the mapping tab is making that error be displayed on your website and I haven’t been able to find this error in the WP support forums yet but will look to find a solution.

    I also updated a small bug in the mapping section so you’ll want to update to ver 3.0.1 once we figure out why that error is being displayed.

    Thread Starter amunalaima

    (@amunalaima)

    Thanks. I tried updating to ver 3.0.1 to see if it would work, but it still gives that same error, and just in that tab. Thank you for looking into it. It will be great once it works.

    Thread Starter amunalaima

    (@amunalaima)

    Also, is there a way to make form be tagged with multiple tags? for example “Website House List” and also be tagged as “Website Homepage Form Lead”.
    Multiple tagging is really important…

    Plugin Author e_durose

    (@e_durose)

    Hi @amunalaima,

    Still working on troubleshooting the ‘lsaquo’ error.

    Also wanted to let you know you can add multiple tags to a contact by separating each tag with */*.

    ie. Tag1*/*Tag2*/*Tag3

    I’ll update this thread when I find any information on the error you’re receiving.

    Thanks!

    Thread Starter amunalaima

    (@amunalaima)

    Excellent thanks! Ill try that.
    And thanks for looking into the problem. It’s so weird that’s happening.

    Thread Starter amunalaima

    (@amunalaima)

    The multiple tags worked! Thanks very much.

    I do have another problem however, the plugin for some reason is adding a tag “gtsr” to contacts in OAP and i have no idea why? It’s really annoying because it keeps adding it to every contact, and readds when i delete. Please advise.

    Plugin Author e_durose

    (@e_durose)

    Great!

    Glad the multiple tags are working. Yes I know what the gtsr issue is.

    It’s a bug in ver. 1.0.

    To fix this in your code you will need to update one line of php in the flie gravity-to-officeAP.php

    Replace line 735: $data ='<contact id="'.$cID.'"><Group_Tag name="Sequences and Tags"><field name="Contact Tags">gtsr</field><field name="Sequences" action="remove">2</field></Group_Tag></contact>';

    With: $data ='<contact id="'.$cID.'"><Group_Tag name="Sequences and Tags"><field name="Contact Tags">$contactTag</field><field name="Sequences">$sequence</field></Group_Tag></contact>';

    Basically updating the value gtsr with $contactTag and the number 2 with $sequence.

    Thread Starter amunalaima

    (@amunalaima)

    Thank you, that worked : )

    Thread Starter amunalaima

    (@amunalaima)

    Hello there!
    Any updates on the “lsaquo” error?

    Plugin Author e_durose

    (@e_durose)

    Hi @amunalaima,

    Unfortunately, no I haven’t been able to figure out the cause of this error yet.

    One lead I found had to do with viewing/working in a language that doesn’t support that character but I haven’t been able to test that out.

    I’ll make sure to post any updates.

    Thanks!

    Thread Starter amunalaima

    (@amunalaima)

    Hello there! Still the error persists. Please let me know of any progress..

    Thread Starter amunalaima

    (@amunalaima)

    Thank you. The new update solved the issue it seems. Thanks!

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘Error makes it impossible to access form mapping tab!’ is closed to new replies.