alsterb

Yeah – just checked on my browserstack account and cannot see any issues – the slider is a bit slow to load, but apart from that.

Sounds like the issue you is on your machine with your cache or history. Download and take a look in chrome if you haven’t got it already or on IE. Like I said try clearing your cache, you need to identify if the issue is local to you, and no-one on here can do that for you!

Which version of mozilla firefox?

I can see a slider with booking / out now etc. and cannot see a cursor or space on the right – it may be a caching issue. I would try checking in another browser or wipe your cache and try again.

Look fine on Safari on Mac – which browser are you using?

As a follow up to the above after it’s been live on the school site for over a month, the school have reported how much time the plugin has saved them with dealing with parents booking after school clubs, and all they need to do now is print off one of the My Tickets reports to use as a register! This has so much potential, especially against some of the more expensive options out there like ticket tailor. Well done Joe!

Exactly what did you copy into the header.php file? Can you copy the section of code, including the parts before and after that you altered?

Have you set your child theme up already? If so, it should include a styles.css file or something similar, that you can then add css changes too. ‘Appropriate CSS’ is any css you require to make custom changes like that I put in the last post.

If you don’t set up your child theme correctly or activate it in the admin area, you will not see any changes!

You’re welcome!

You need to delete these lines, probably in your header.php template:

<span class=”icon-bar”></span>
<span class=”icon-bar”></span>
<span class=”icon-bar”></span>

And replace with something like:

<h4>MENU</h4>
<i class=”icon-arrow-down”></i>

You’ll need to add some CSS to get the arrow in place, such as:

.icon-arrow-down:before {
content:”\f063″;
}

Hope this makes sense!

If it’s the theme here: https://modernthemes.net/demo/?theme=Sensible

Maybe try this CSS?:

body.blog .col-9-12 { width: 100%; }

Currently it’s set to 75%, just make sure you pinpoint the blog body class to avoid altering it on all pages!

Hi Cheslp01,

Which theme are you using? Eg Twenty Thirteen, or maybe a custom theme?

UPDATE: Just needed to update the plugin plus WordPress core, doh!

Thanks Joe for coming to the rescue…!

Hi Joe,

I’m also having an issue with Paypal identical to that of gilbertovb – can I confirm that it’s normal when saving the PayPal email and Merchant ID in the admin are and then saving the settings that the form fields for PayPal email and PayPal Merchant ID go back to blank? I’ve also searched the database and cannot see where they are stored, so I’m wondering if it’s not storing them correctly…? ~If it helps I can always send you a screenshot or access to see the problem firsthand…

Like gilbertovb when I try to make a PayPal payment, it says there’s a problem with the sellers email:

We cannot process this transaction because there is a problem with the PayPal email address supplied by the seller. Please contact the seller to resolve the problem.

Thanks, Alex

Ps. I don’t want to look like I’m taking advantage, since your plugins are great and so is your support so I just made a donation!

Thanks Joe, I’ve just gone onto a fresh install of wordpress I did to look at this, and replaced the plugin with the development version you pointed me to. It’s definitely storing it now – it appears at the cart stage which it didn’t before, and I can now see it when editing payments in the back-end.

These are the only two places I imagine the custom data shows up after entering it, so I don’t imagine there’s any more probs there.

Thanks for your speedy support – top plugin from a top developer.

I will make sure to send you a donation once things are up and running!

No problem – I’ve tested it now on both the sites I applied it to, and both have the same issue, I just didn’t realise first time that I’d been logged in when I tested it…