- antoniooiAsked on July 13, 2012 at 01:48 AM
All the while, all my FB integrated forms were working fine until recently, the Facebook Login Button has gone missing and all my users are unable to submit their information to me. Please note that this is mission critical and your immediate action to rectify this problem is highly appreciated.
FYI, I need to use the display faces option because if I don't, your blue color Facebook login button will keep appearing even after the users have clicked on it and logged on to Facebook. This is rather misleading and confusing. But when the show faces option is selected, the Facebook login button is entirely not appearing except the label: "Please logon to Facebook first." -- without the button (see attached screenshot)!
Please note that it isn't caused by my custom CSS that adjusts the positioning of my Submit button in order to make it align with my page separator's BACK button. Even though without the CSS, the FB login button still missing.
Please be reminded that if your forms keep screwing up our business and company reputation, we just can't proceed to your premium subscription, we can't -- that will be a very hard decision for us to make. I hope your team can understand that.
Thank you and expecting for your prompt response.
- JotForm SupportNeilVicenteAnswered on July 13, 2012 at 10:33 AM
I understand how you feel about this issue. Sorry for any troubles caused.
After doing some tests, I found out that this problem occurs on forms with page breaks.
With that said, I have forwarded a ticket to our developers. This is an important issue, so I assure you that this will be given a high priority among our development team's tasks.
We will inform you as soon as we have fixed the said bug.
- antoniooiAnswered on July 13, 2012 at 11:00 AM
Thanks a lot Neil! Imagine now all our customers need to submit their information to us through email! @_@
- JotForm SupportNeilVicenteAnswered on July 13, 2012 at 11:18 AM
In the meantime, you can remove the form's integration with Facebook just so your users can submit the form without problems.
- antoniooiAnswered on July 13, 2012 at 11:29 AM
Without the FB integration, I can't identify the user who submitted it -- This is the problem! You just can't ask me to intruction them to enter their name for each submission. This will cause two major problems here:
1. "MalaysiaTraining.net sucks!" -- from the customers.
2. Anyone can put someone else into trouble by simply enter someone's name instead of their own. Our clients are basically competitors to each other. They are training providers.
- antoniooiAnswered on July 25, 2012 at 04:15 AM
Still no solution for this?
- JotForm SupportjonathanAnswered on July 25, 2012 at 05:55 AM
I just tested your form... but I could see the FB login button?
Even on Neil's test form with pagebreak element, I could see the button
Please correct me if I am looking at the wrong FB button instead.
- antoniooiAnswered on July 25, 2012 at 06:08 AM
Then why Neil responded to me with this message?
"After doing some tests, I found out that this problem occurs on forms with page breaks.
With that said, I have forwarded a ticket to our developers. This is an important issue, so I assure you that this will be given a high priority among our development team's tasks."
Or your programmers had fixed the bug but forgot to feedback to me on this post?
Anyway, I hope this problem will not return back again. Thanks a lot!
- JotForm SupportjonathanAnswered on July 25, 2012 at 06:21 AM
It is possible that at the time Neil was at your service, he was able to reproduce the issue with page break and FB login combination. I could see he even submitted a ticket for this and provide 2 forms to demonstrate the issue.
But as of this time, when I tested all the forms (yours, and 2 of Neil's), I could easily see the FB login button that in your original screenshot and Neil's form are missing.
Our dev team had not updated the ticket though... and they normally updates the post/thread whenever they fixed a submitted ticket. So, I cannot provide the info for now what transpired (or what fixed it)
If the issue seems to be fixed on your end , please try also to be still cautios and observant of your live forms with FB login on them.
This post will still be updated officially by our dev team when new updates are available.
- antoniooiAnswered on July 25, 2012 at 06:26 AM
Thanks again Jonathan. But frankly speaking, sometimes those inconsistent and uncertain issues of JotForm really driving me nuts (if you can look at my other post that I posted earlier: http://www.jotform.com/answers/116188-JotForm-is-still-using-user-history-data-for-submission#2)
- JotForm SupportNeilVicenteAnswered on July 26, 2012 at 08:47 AM
The ticket I have forwarded was already assigned to one of our ever-dependable developers. It's just that their workload is a little too heavy that we cannot commit to an exact time for a bug to be fixed.
Moving on to your issue, I just realized now that I could have suggested replacing page breaks with form collapses. To be honest, I myself am quite baffled as to why I did not think of this solution when I was dealing with your problem.
I did some tests a while ago and found out that form collapses are perfect alternatives to page breaks on your form - at least until the original problem is resolved.
Kindly try it out then let me know what you think.
Note: Be careful when deleting the page breaks. Make sure that you are deleting the page breaks and not the other fields in your form.
- antoniooiAnswered on July 26, 2012 at 09:41 AM
It may not be so perfect when:
1. The later section of the form is CONDITIONALLY depending on the earlier section.
2. When we the sequence is important and we do not want our users to randomly jumping here and there.
3. When we have too many sections, e.g. 5 sections or above, the inactive sections takes up too unnecessary space of the form. Don't forget that at least 1 section must be remain opened all the time.
But I haven't really tried out your Form Collapse feature yet, especially when comes to conditionally control the visibility of the section separators/headers. I just presumed that your Form Collapse is using some sort of jQuery Accordion bahavior (if I'm not mistaken).
I hope your team can rectify it ASAP.
As for your team's workload, being a former software architecture, I just want to share with you my experience here:
As we all know, every new product causes the most bugs unless otherwise constantly fixed and eventually become a stable version. However, many technical teams don't really realize that 'stable version' of each product releases the most resources. Due to this nigligence, many software companies keep continue developing new products or cloud apps right after the release of old product and began to put less significant amount of focus and resources on older yet unstable products. As a result, old products and new products keep competing for resources with each other.
My advice is: Stabilize all the existing products and clear all the bug lists BEFORE proceed to the new product development. Repeat the same for every new product. Don't rush for the release of multiple new products. With this good practice, 1) your team will not get interrupted (or less interruptions) by old bugs during their new product development; 2) Your old products will not hold back your resources for your new product development and hence secure your expected release date.
It is useless to release thousands of product when almost all of them are unable to achieve certain level of user satisfaction. Eventually, all customers runaway and we can only use our numerous products to build our own 'grave'.
If you think this is not up to your decision level, please help me to forward this to your top management -- just say that this is the request from one of the customers.
Owner and founder of OTK Web Solutions & MalaysiaTraining.net
MCP, MCSD, MCTS, MCT