Hi gretagreiss,
Can you tell me an example of a customization you’ve made that should appear? Also, how are you making the customizations? Are you loading a custom stylesheet? Using a plugin? Otherwise I don’t know what I’m looking for.
How can i send you screenshot?
Hi gretagreiss,
Actually, what I’d like to know is the CSS code that you’ve modified and how you went about modifying it. I can check to see if the code is actually getting enqueued or not, and when it’s getting enqueued.
Ok, basically i did some changes on the booking-form.css
For example i add a border
.rtb-booking-form fieldset {
border: 1px solid rgba(0, 0, 0, 0.1);
margin-bottom: 1em;
padding: 1em;
}
i changed the size of my labels
.rtb-booking-form legend {
padding: 0 0.5em;
font-size: 18px;
}
i changed the add message button
.rtb-booking-form .add-message {
margin-top: 2em;
font-size: 1.2em;
text-transform: uppercase;
background-color: #393939;
width: 10em;
padding: 0.5em;
font-weight: 600;
text-align: center;
}
and more stuff like margin padding
Many thans to helping me 🙂
Hi gretagreiss,
Yes, this is an issue with your theme’s preloader which generates the seamless page-to-page transitions. In short, the theme is broken. Unfortunately, ThemeForest has a long record of approving and selling themes which break core WordPress functionality like this.
You may be able to workaround this problem by enqueuing the assets in the head on every page. It will increase your site’s overall asset payload, but it should get around the preloader issues.
You can install and activate this micro-plugin to enqueue all of the Restaurant Reservations assets in the head. Click the Download Gist button on the right, upload the .php file to your /wp-content/plugins/ directory, then activate the “RequireJS Compatibility for Restaurant Reservations” plugin from the plugins list in your WordPress admin panel.
If that works for you, please let me know and I will try to follow-up with the theme developer.
Yes! It works but there is another bug that i don’t know how to fix.
In the Date row the authomatic calendar is not shown and,a s the layout style, if i refresh my page so then the calendar appears.
Check it http://vicino.es/test/reservation/
Thanks
Oh damn. Yeah, I see the problem and I don’t know if there’s a workaround for that. I think you’ll need to go to the theme developers and ask them for help. Here’s the issue.
When the JavaScript is loaded, it looks for the booking form and registers the events (like loading the date picker on the form elements). But since the JavaScript gets loaded and run BEFORE the booking form has been loaded into the page, it never registers these events.
At the moment, Restaurant Reservation’s booking-form.js is not configured to be executed again. So I’m not aware of a workaround that would jive with your theme’s “seamless” page transition function. Sorry I can’t be more helpful!
If you contact the theme authors, please let them know that they can contact me if they want help figuring out a solution to the problem.
I will contact the authors today! I will mantain you update.
This is a great Support!
Many Thanks
I think i found the solution, http://vicino.es/test/reservation/
Just changing the way of transition between loading pages. Before it was fading and now no animations!
Tnx for yout time 🙂
Great! I’m really glad you were able to turn off the transitions. Those always present compatibility problems.
If you have a moment, I always appreciate reviews for the plugin.
Hi, Sorry for bothering you again but it seems that the plugin is not working good on mobile phones. I saw that the calendar and the time are not showing properly on my mobile device (i’m using an iphone 5). When i want to pick date and time i view a withe background. But if i scroll down till the end, finally y can see the caledar and timetable
Could you please check it out? http://vicino.es/test/reservation/ (in a mobilephone)
Many Thanks
Hi gretagreiss,
Yes, there is a bug with the date and time picker on iOS 8 at the moment. I’ve been keeping a close eye on the pickadate.js library for a resolution to this issue. Unfortunately, the fix that went in caused more serious issues in other browsers.
As soon as a fix is available I will ship the new version in an update to the plugin. But until then there is little I can do. I have tried hard to work-around the existing issues and find good-enough-for-now fixes to the problem, but everything I’ve tried has only caused more problems.
Oh, no :(.. Do you have any idea about how long it will take to fix it?
