[Barry]

Fantastic, I look forward to hearing back from you 🙂

[Barry]

This reply is private.

[Barry]

For sure, we’ll be here 🙂

[Barry]

This reply is private.

[Barry]

Sheryl,

We’d be happy to.

Since I don’t see the same problem as you are facing though I’ll need more information. Would you be down to share a database dump? Plugins like Duplicator are great for this if you’re not sure how, as in fact they go a step further and share your plugins with us, too.

If you’re able to do that and – depending on the size of the file – share it directly here or via a Dropbox or Google Drive link (or similar), that would be great. You can of course do so via private reply.

Thanks!

[Barry]

Fantastic, glad that helped 🙂

I’m going to set the status of this topic to ‘pending fix’ and, as soon as we are able to ship a substantive fix in a future release of the plugin, we’ll post an update in here (so you can remove the customization).

Thanks again for your support and patience with this.

[Barry]

This reply is private.

[Barry]

This reply is private.

[Barry]

Thanks for sharing it 🙂

So am I correct in understanding it is only an issue when that specific shortcode is used?

It doesn’t look either like one of our own shortcodes nor something that Advanced Post Type Order provides … is a further plugin required to see this issue and (unless of course you hit this same problem on a ‘regular’ event view) is it possible the conflict lies with that other plugin?

Thanks!

[Barry]

Hmm, I think that’s the same version I can obtain from the WordPress plugin directory, isn’t it? The error you cited though specifically references code from the Pro/Advanced version, which we do not have access to.

Just in case, I did attempt to replicate using the free version/the version you attached, but I was unable to replicate the error.

Here’s what I suggest from here:

• If we need the Pro or Advanced version to see this problem, please attach it or we aren’t going to be able to test this out
• Please also confirm which event views (or admin screens) specifically I should be able to see the error on

Thanks!

[Barry]

OK, well I’m happy to hear you found the source of the problem and were able to resolve it 🙂

Given that and since you marked this topic as resolved I’ll go ahead and close it — but of course please don’t hesitate to open new topics as needed if we can help with anything else.

Thanks!

[Barry]

This reply is private.

[Barry]

This reply is private.

[Barry]

This reply is private.

[Barry]

This reply is private.

[Author]

Posts