Calendar View works on a FW7/Backdraft site but only locally with Mamp.
It fails to work when uploaded to a browser.
Why would this be ?
Richard
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
There is a bucketload of javascript on that page and I am seeing quite a few errors.
Try on a clean fresh page with less stuff and see if it works there - possibilities of a javascript clash.
David
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks David
I have tried various changes one of which was to change the page from php to html and then it worked. Except of course I would like it to be a php page in order to use a CMS (webyep)
I will continue to experiment - outside of the backdraft framework probably
Richard
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
You should also set the HTML type for your Date inputs to ‘Date’ and then you will get native operation in iOS etc.
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Ah ! Thanks. One more thing you have taught me !
R
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Well - Calendarview works inside a php Backdraft page as long as Webyep is absent. I tested it in a freeway template with Webyep and that does work. Although - unlike Backdraft’s version - it is not in a table . Just text fields laid out in a Div.
One thing I have yet to overcome - I have set the HTML type to ‘Date’ following David’s advice and so get the native operation on an iPhone. But the Calenderview date picker also shows too. Is there a way to deactivate Calendarview at the breakpoints for the smaller media types ?
Richard
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Try this in Page>Html Markup in the before end head section Before
<style type="text/css">
@media screen and (max-width:480px)
{
div.calendar.popup { display: none !important;}
}
</style>
David
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks David, that worked - However there is an oddity.
I have two text fields - Arrival & Departure. Set to Date in HTML type
Calendar View works and with your code it does not show in iOS. But the second input field on an iOS device (an iPhone) does not function - the field with a reveal arrow is there but does not respond.
Remove Calendar View and they both respond.
Further more Chrome seems to have its own date picker built in when these fields are set to Date. As a result with Calendar View action applied I get two date pickers popping up. Safari and Firefox just give me the Freeway version.
I think if I am going to get moving on this site I will have to abandon Calendar View and just go with Date. Chrome users wlll get the date picker on regular screen, as will phone and tablet users. The rest will have to enter the date as text.
But thanks for the bit of code - I will will keep it on file should a comptable Calendar View action becomes available.
Regards
Richard
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
But the second input field on an iOS device (an iPhone) does not function - the field with a reveal arrow is there but does not respond.
Is it online?
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
http://www.richard-lowther.com/1001/contact2.html
has the CalenderView applied
(http://www.richard-lowther.com/1001/contact.html is without calendarView)
Richard
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
But the second input field on an iOS device (an iPhone) does not function - the field with a reveal arrow is there but does not respond.
It certainly does for me using iOS 8.3
However I do see an issue at smaller screen sizes because even though the Calendar View does not show the javascript is expecting input (a click on the calendar) before it will proceed.
You may have the same issue on earlier versions of iOS
So in conclusion - yes I agree, probably best to do without Calendar View as the extra code to disable the javascript at smaller screen sizes is not worth the effort.
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks again - Interesting
Out of curiosity I will check it this weekend on some friends devices including an iPad and non-apple devices. But meanwhile for the site I will follow your view and do without it. Doubtless it will all go peculiar again when I change to php and add Webyep. Or maybe I should just leave well alone and keep it as a stand alone page in html !
Best wishes
Richard
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Doubtless it will all go peculiar again when I change to php and add Webyep
If the page isn’t going to edited by the user then why have WY in there?
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Well, initially the contact form was going to be at the bottom of a page above which would besome editable text and a google map. But I am thinking to leave as is now, on its own with no need to be edited by the user.
I might, if and when I have the time, just run a test to see what happens if I do add the CMS. Just out of curiosity (and before I offer it as an option to anyone!)
R
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
WebYep has a Prototype version (originally, that was the only version) in addition to jQuery, so you have that option as well.
Walter
On May 28, 2015, at 5:08 PM, Richard Lowther email@hidden wrote:
Well, initially the contact form was going to be at the bottom of a page above which would besome editable text and a google map. But I am thinking to leave as is now, on its own with no need to be edited by the user.
I might, if and when I have the time, just run a test to see what happens if I do add the CMS. Just out of curiosity (and before I offer it as an option to anyone!)
R
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options