cambofrizz

Creating a new calendar only for the countdown to work properly seems to me the least logic and in any case inconvenient.

Including a setting in the choices to override the default sorting is
a) not so difficult
and
b) much more logical

But, as I’ve noticed before, it seems especially @rochesterj considers SportsPress a finalized project, which doesn’t need any adjustments whatsoever.

Hi @savvasha ,

Ah yes, you’re right, the calendar is set to order by matchday, which makes sense for the calendar, especially in list view.

However, I still think it does not make sense for a widget supposed to display the next match. So, there should either be a setting to override the default sorting (like I have done in the countdown code), or the selection for the countdown source should not be a calendar, but rather a league and season.

Further clarification: when manually selecting the teams for a League the League Table displays results correctly in original language and translations. Only when clubs in a League are set to ‘Auto’ the League Table in translation shows no results.

I’ve not received any response to my questions on the Polylang support forum and on top of that the latest version of their plug-in causes even more trouble. So, it seems you’re right and it’s a Polylang problem.

So, I’ll mark this as resolved, not because it is, but because it’s not a SportsPress problem. Thank you for your time.

The latest version brings no solution. Instead, it’s even worse. When now trying to Update I get:

Warning: array_flip(): Can only flip STRING and INTEGER values! in **********\wp-content\plugins\polylang\include\translated-object.php on line 258

and:

Warning: Cannot modify header information - headers already sent by (output started at **********\wp-content\plugins\polylang\include\translated-object.php:258)

When going to ‘Languages’ the same warning as above is displayed. A new language is now added without any value (so empty) and I’m unable to delete it.

Right, on top of getting no support here whatsoever, it’s getting worse and worse which makes me now switching to WPML and saying goodbye to Polylang forever.

On the SportsPress support forum linked above, they are not sure whether the conflict is caused by their plug-in or by Polylang.

Is anyone on the dev team here ( @chouby @manooweb @raaaahman ) even interested in this problem?

You don’t understand the issue correctly, Polylang uses different posts for each language and connects them, just like WPML does.

You’re assuming this and that and using ‘looks like’, ‘seem that’, while you don’t even know what you’re talking about.

Do you even care much about SportsPress? I surely get the impression you don’t and consider it a ‘finalized project’.

All kinds of ‘enhancements’ are ‘promised’ to be in ‘the next update’. However, the ‘next update’ is never announced, let alone implemented. Indeed, many suggested ideas on their forum are ‘accepted’ as being ‘very good’, but some of them got that label several years ago, and nothing has been done with these ‘very good ideas’.

And it’s not just that there’s no real roadmap, also issues reported in the support forum are either not addressed at all, or they’re labelled ‘resolved’ when they are absolutely NOT.

I really wonder what kind of people are behind this plug-in. The more I work with this ‘plug-in’, the more I resent it, to be honest.

It’s probably a bit better to have it as:

if( $obj && !in_array( $obj->name, $exclude ) ) {

but you get what I’m at I hope.

The question remains: is it something you should change or something Polylang should change? Haven’t tested this with WPML, but if it doesn’t occur with that plug-in, then it’s maybe Polylang after all that should make a change?

Anyone have more insights?

• This reply was modified 4 years ago by cambofrizz. Reason: more clarification

I have posted this problem on the SportsPress support, too. And I seem to have found a solution which is not related to Polylang but indeed to SportsPress. Unless when you check my solution and think: “Oh wait, we can prevent that from happening”. If that’s the case, please let me know.

I’ve made a small change in the function sp_taxonomy_field (in sp-core-functions.php) which seems to do the trick.
I’ve changed lines 1506 and 1507 from:

$obj = get_taxonomy( $taxonomy );
if ( $obj ) {

into:

$obj = get_taxonomy( $taxonomy );
$exclude = array( 'language', 'post_translations' );
if( !in_array( $obj->name, $exclude ) ) {

Maybe there are better ways to do this. If so, please let me know.

OK, one more additional clarification, which I think might be the reason it goes wrong and is maybe not related to this plug-in but to SportsPress.

The ‘Details’ section has a php function to include CPT-depending input fields, they are called with

<?php
	foreach ( $taxonomies as $taxonomy ) {
	sp_taxonomy_field( $taxonomy, $post, true );
	}
?>

When I remove this, the ‘Language’ heading and inputs disappear, along with of course all the other (needed) inputs like ‘League’, ‘Season’, etc. But I can edit and save now normally, without a strange language number added.

Right, found the culprit but I’m not sure whether Polylang should prevent being included with the above ‘foreach’ or whether SportsPress should change the call for taxonomies to exclude Polylang’s. I will post this problem on their support thread, too.

In addition to the above and maybe helpful: in the example of a ‘Calendar’ post type, in the ‘Details’ section (with dates, league, season, etc.) Polylang adds a section called ‘Language’ (sp_calendar-language-field). Underneath is a select input to choose a language. I wonder why that is needed, when the main setting of the post is already set to a language.

Furthermore under the Language section is another – without a heading – called ‘sp_calendar-post_translations-field’ with initially a link “+ Add New Tag”. I also wonder why that is there.

Can someone please look into this very annoying problem which makes Polylang unusable with SportsPress. I’m about to give up and switch over to WPML.

OK, thanks for clarification, but why is it not possible to select where the H2H tiebreaker comes into play? That would solve some of the problems.

So, in the end (where my requirement is to have H2H as the second criteria, after overall points), I’m correct to have to disable the goal difference as a ranking factor. Right?

Just so you know that in many (major) soccer leagues that IS the second criteria. So, sorry, but saying “it works for most of our customers” does not impress me.

And for upvoting the idea in your forum: I already did.