Mark O'Donnell

Thank you very much for the detailed listing of the error. I believe all these messages are coming from the error with __contstruct(). This is a common error I see when working through PhP 8 upgrades. (One which I seem to remember fixing but that may have been a different plugin.) I will try to find time to fix the problem this weekend. Stay tuned.

-Mark

Super. I now have a PHP 8 test environment and will be working through all the plugins. I will be posting new releases as needed.

Yes, things look fine on 7.4. The issue is PHP 8. Unfortunately, it’s going to take a bit to get my local test environment updated to PHP 8.1, but stay tuned, I’ll get there. I expect it to be a straightforward fix, I just can’t seem to see it without “breaking it”.

-Mark

Got it. Thanks.

Thanks for posting here and for the diagnostic info. That’s helpful. What data are you most interested in, I’ll check that out first after it installs.

-Mark

Sorry, I’m away from my development computer until July so I can’t dig into this right now. But here are some quick thoughts:

o Most of the data is WP custom post types which can be exported/imported using the built in WP tools. You may have to export the DB as well.

o The MSTW CSV Exporter worked once upon a time, but I’m pretty sure it is out of sync with League Manager. Mileage may vary.

o You can import the data using the plug-ins CSV Import function. You may have to re-enter all the data into Excel, but that is sometimes much faster than entering it into the plug in.

If you have no luck, ping me again after 4 July and I will dig in a bit more with the code (the only guaranteed accurate documentation LOL) in front of me.

-Mark

I see it happening on your site but I have not been able to replicate this behavior on either of my dev sites. Please tell me the EXACT shortcode you are using so I can duplicate it.

Ok. Thanks. What is the EXACT shortcode you are using so I can make sure I am doing exactly what you are.

What is the <span style=”text-decoration: underline;”>exact incantation</span> you are using for the mstw-tr-roster-2 shortcode?? As a quick fix, you might try something like this:

mstw-tr-roster_2 team=vendettabrimhallblack18u roster_type=baseball sort_order=numeric

Hi Roy,

Thank you for posting here. I have not been able to reproduce this behavior (yet) but on your page you will notice that when you follow the link the first time the roster is sorted by player Last Name, but the sort control shows Jersey Number (and the player data is missing). If you then sort (again) by Last Name, voila, the player data appears.

All that tells me that the initial sort order is being passed as jibberish (by the link), so the control shows the first choice in the list, and the code sorts based on some other default choice.

I will dig into the code and create a patch as soon as I can. I expect it to be a simple fix, I just need to carve out a little time to dig in.

Stay tuned.

-Mark

Sure. Players are WordPress Custom Post Types. There’s an argument – exclude_from_search – used when creating a CPT with register_post_type() . You can make this happen without changing the plugin’s code by adding a snippet of code to your child theme. There are several explanations of this process on the web including https://www.forge12.com/en/blog/stop-wordpress-search-showing-custom-post-type/

-Mark

Thanks for providing the link to your page, that helps a lot. I see what you are referring to. It appears I have to do a bit of work on the [mstw-tr-roster-2] shortcode’s responsiveness. I’m a bit confused about this, since I thought I had checked this out in testing, but something is not quite right. I will take a look and see what’s up.

-Mark

Hi Bjorn,
I’m sorry you are having such difficulty. But wow, great job!!

If I understand what you did in paragraph 1, it’s pretty clearly not a plugin problem. (I’m glad to hear that at least.)

I’m not quite sure about para #2 but my question about #1 and #3 relative to #2 is:

If I understand correctly, you had no other plugins installed in paras #1 and #3, correct?
It also appears you may have other plugins active (not too concerned about installed) in #2. If so, have you deactivated all the other plugins and tried with just MSTW Bracket Builder??

It would make the most sense to me if there’s a plugin collision somewhere, not a theme collision.

Otherwise, I can’t think of anything else it would be. But clearly something is not right. I agree that the premium version is unlikely to help at this point.

Don’t worry about my time. No problem. There is something important to learn about WordPress with every new “puzzler”. I’m sure there will be when you figure this out too.

Regards,
-Mark

Okay. Let me know. It could also be that the DB is somehow munged up. That would be a bit of a surprise to me, but the data is not removed when you delete the plugin, so re-installing won’t fix a data problem.

Another option is to try the premium version. This is not a sales pitch, but I believe it to be a more stable product (it gets a lot more attention) and certainly a much more feature rich product. If you have the same issue(s), something is definitely up on your end.

-Mark

Okay, I just re-tested this. Could not generate these errors. Here’s the edit tournament screen and the resulting shortcode output.

I also checked out a 5 round tourney I built for 1.3 testing. Here’s the Edit Tourney Screen, the bracket shortcode output, and the table shortcode output.

Everything looks okay on my end. So my guess is our environment’s differ somehow. The problem is generally PHP or WordPress versions (we seem okay here based on the info you provided) or conflicts with the theme (usually that is front end/shortcode display issues) Based on the debug.log you sent, or conflicts between plugins. In your case, it could be inconsistencies between code versions. So I suggest:

1. Load version 1.3 straight up, removing any and all code changes you may have made. Delete the previous version, then load and activate the new version from www.remarpro.com.

2. Deactivate ALL other plugins. Re-test. If there’s no problem, re-activate the plugins one by one until you find the culprit. Then we can see what’s up. It’s usually not hard to resolve the issue once it’s identified.

Viel Gluck. Bitte lassen sie es mich wissen.

-Mark