Andrew Messier

Thank you so much for updating your review.

I updated the readme to provide an example to hopefully make this more clear in the future. I also noticed an unrelated bug while troubleshooting this thread which I just committed a fix for (1.1.3).

Thank you again and please let me know if you have any more issues, requests, etc.

Hi Bj?rn,

Are you referring to the light gray on the table row? If so, it’s because the tables are striped (alternating colors). If you would like to get rid of the alternating colors, I can provide custom CSS for the Additional CSS section of your template.

Some additional troubleshooting after the above, it doesn’t look like the REST API is enabled. If I navigate to https://folsompickleballclub.com/index.php?rest_route=/wp/v2/stb-tournament/1944 I can see your tournament (titled Pickelbowl with competitors Ling, Cheryl, etc).

If I navigate to https://folsompickleballclub.com/wp/v2/stb-tournament/1944, I receive a 404 (indicating REST is disabled).

Seeing the data at the first route is great because it shows it is indeed working, you just need to enable the REST API and correct your shortcode. Thank you and feel free to let me know if you need any more assistance.

Thank you for messaging back. Would you try it again without the dollar sign?

[simple-tournament-brackets tournament_id=”1944″]

Hi There! What issue are you experiencing? I’ve verified it works using the latest WordPress. Is the REST API enabled on your site?

Hi There!

Tournamatch does not come with a built in payment gateway. The myCred integration will permit your registered users to spend tokens (or whatever you label the currency in myCred) to register for ladder events, tournaments, and challenge wagers.

Using WooCommerce with myCred would provide the best experience for your users in my opinion, though it isn’t necessarily required. You could use a different payment collection system and manually adjust token balance in myCred.

Hey there!

I apologize for the very late reply. I’ll take a look at this and see if there is anything we can do via an update. I’ve clicked through several of the screens and this looks like the only one that I observe with an issue. Do you happen to know if any other views are affected?

Thank you for reporting this and for your patience.

Thank goodness! I’d love to know what was off in the apache2.conf. I run a similar setup locally and it might help me some day.

Okay if you don’t share – I’m happy it’s working for you.

Ok. That tells us mod rewrite isn’t working correctly. I recommend we get that fixed before moving forward. Let me look around and see if I can find some troubleshooting steps.

Disable the plugin, set permalinks to post name, and verify there is no rest API error.

Based on the API error you observed, it sounds like your server doesn’t have mod_rewrite enabled or working correctly. Note that the error you observed (about the rest API) is a WordPress error, not a plugin error.

I think I can deploy an update to workaround the issue, but that won’t resolve the server issue.

I think I might have figured this out. Will you verify whether setting permalinks to post_name makes a difference?

How are you hosting PHP? Apache, nginx?

The main API endpoint can be found here: https://r3eds.ddns.net/R3EDs/wp-json/wp/v2/

If you don’t have any other plugins enabled, it’s possible your web host might be disabling REST. Who is your webhost?

Hi z0dnet,

Thank you for sharing a link to the page. I took a look and the REST API call that is made returns a 404 (not found) error. If I navigate to the standard REST API on your website, it also returns 404. This tells me that the API is not enabled on your website.

Do you happen to have any security plugins installed that might disable REST API? This is the typical cause of the issue you have.