Toggle Submenu
  1. Forums
  2. Recent
  3. Categories
  4. Tags
  5. Users
  6. Badges
Support is currently Offline
Support Offday
Today is our off day. We are taking some rest and will come back stronger tomorrow. Promise!
Official support hours:
Monday To Friday except Saturday and Sunday
From 09:00 To 16:00
Add a reply View Replies (10)

Resolved Problem with fangate and RSForm

0
Votes
Undo
  1. coziosco
    coziosco
  2. Bug Report
  3. Friday, 15 February 2013
  4.  Subscribe via email
Hi

Great work on ffgate. Looking really good :-)

I'm in the middle of trialling ffgate to run a fangated competition. Everything is working fine apart from the integration between the fangateing and RSForm Pro (used so end users can answer the questions)

With Fangateing switched off (basic options>public set to yes) everything works very well. Everyone can see the facebook app, fill in the form and enter the competition.

However with fangate switched on (basic options>public set to no) the fangate works fine, however once users have filled in the form and pressed submit a 'users from facebook aren't allowed to access this page directly' error is shown.

I'm pretty sure everything is setup correctly and it's the public yes/no causing the problems.
Any ideas how I can achieve a fangated form??

https://www.facebook.com/LyonOutdoor

Cheers

C
0
Responses (10)
Yves Hoppe
Yves Hoppe Accepted Answer Pending Moderation
Support team
0
Votes
Undo
Hi,

hmm probably the sec_key (Security key) is missing after the RSForm Pro form is submitted. You could try inserting it to a hidden input in the RSForm (not sure that this is working, have a try) or add it to the result url (&sec_key=xx).

Best regards,

Yves
  1. more than a month ago
  2. Bug Report
  3. # 1
coziosco
coziosco Accepted Answer Pending Moderation
0
Votes
Undo
Hi Yves

Thanks for the super quick reply.

I've tried pasting in &sec_key=verysecurekey here there and everywhere in RSForm Pro with no luck. still getting the same error message.

I've a feeling it may be in form attributes or the PHP scrips section of RSForm Pro but not too sure :-(

Is it worth trying to get it to work with RSForm Pro or is it easier to switch to a different form tool which is easier to use with ffgate?
  1. more than a month ago
  2. Bug Report
  3. # 2
Yves Hoppe
Yves Hoppe Accepted Answer Pending Moderation
Support team
0
Votes
Undo
Hmm don't know RSForm Pro very well, but i took a look at the description - you should be able to add a hidden field, name it sec_key and set the value to verysecure (it's just like a normal input field but not shown).

Best regards,

Yves
  1. more than a month ago
  2. Bug Report
  3. # 3
coziosco
coziosco Accepted Answer Pending Moderation
0
Votes
Undo
Hmm, thanks again.. Still no joy tho. You can see it in action at

https://www.facebook.com/LyonOutdoor

The app is hidden a little with the heading 'win a signed copy of...'

I'm stumped. :-(

I know it's a bit beyond the call of duty but if you want to try things in the backend let me know.

C
  1. more than a month ago
  2. Bug Report
  3. # 4
Yves Hoppe
Yves Hoppe Accepted Answer Pending Moderation
Support team
0
Votes
Undo
Hi,

aye backend access would help - you could also add me on Skype (yves.hoppe).

Yves
  1. more than a month ago
  2. Bug Report
  3. # 5
coziosco
coziosco Accepted Answer Pending Moderation
0
Votes
Undo
I've added you to the admin area and sent you a IM on skype.

C
  1. more than a month ago
  2. Bug Report
  3. # 6
Jeppe, F10 Media
Jeppe, F10 Media Accepted Answer Pending Moderation
0
Votes
Undo
Any luck with this issue?

Thanks.
  1. more than a month ago
  2. Bug Report
  3. # 7
coziosco
coziosco Accepted Answer Pending Moderation
0
Votes
Undo
Yes! Thanks to Yves for the help the following worked fine.. I have the following info stored in my notes which allowed RSform pro to work correctly. Yves did note that it's not 100% secure after this, site will be directly accessible.


You have to change: components/com_ffgate/views/site/tmpl/default.php on line 74

Just comment the line out and add a new line echo JHTML::_('content.prepare', $this->site->html_text);

C
  1. more than a month ago
  2. Bug Report
  3. # 8
Jeppe, F10 Media
Jeppe, F10 Media Accepted Answer Pending Moderation
0
Votes
Undo
This works great.
Thanks.

I will see if it works with RS Firewall as well, for extra security.

/Jeppe
  1. more than a month ago
  2. Bug Report
  3. # 9
coziosco
coziosco Accepted Answer Pending Moderation
0
Votes
Undo
Yep, Works fine with RS Firewall.

C
  1. more than a month ago
  2. Bug Report
  3. # 10
  • Page :
  • 1


There are no replies made for this post yet.
However, you are not allowed to reply to this post.
or Ask a Question

Categories

General
  1. 3 subcategories
Billing
  1. 4 subcategories
Hotspots
  1. 11 subcategories
CComment
  1. 11 subcategories
Matukio
  1. 6 subcategories
CMigrator
  1. 4 subcategories
CForms
  1. 2 subcategories
International Zone
  1. 10 subcategories
Free extensions
  1. 47 subcategories
Archive
  1. 15 subcategories

Last questions

Phượng Nguyễn
Phượng Nguyễn
error download
Hi, when I try to download JEDchecker 1.7 always get a '404 - Not found' error....
0 Replies
Posted on Saturday, 21 July 2018
  • New
    • Thomas Kirchhof
    Thomas Kirchhof
    Migration fehlerhaft?
    Hallo, nach dem Installieren und der Migration (alle vier Balken waren grün) kom...
    8 Replies
    Posted on Thursday, 19 July 2018
  • New
    • David Ziegler
    David Ziegler
    Veranstaltungsliste: alle Veranstaltungen auf eine
    Hallo, irgendwie werden in meiner Veranstaltungsliste nicht alle Veranstaltunge...
    5 Replies
    Posted on Thursday, 19 July 2018
  • New
    • Niamh Manek
    Niamh Manek
    Can't upgrade to Pro version using cinstaller
    Hi, I tried out the core version of Hotspots and liked it, so I purchased a su...
    8 Replies
    Posted on Sunday, 15 July 2018
  • Resolved
  • New
    • Florian Bauer
    Florian Bauer
    DSGVO Datenschutz Checkbox
    Hallo, ich habe gerade auf die neueste Version upgedated, weil ich eine Checkbo...
    15 Replies
    Posted on Thursday, 21 June 2018
    • #GDPR