When the support for a search engine that requires verification parameters is enabled, the module should verify that the verification parameters are really set.

Comments

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Closed (won't fix)

From #464980: Remove search engine authentication/verification code we are removing the engine verification code as it has become out-of-scope for the module. Marking as won't fix.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Closed (won't fix) » Active

So far, the other task has not been accomplished, yet. Only when the other task will be fixed, this task can change status.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

So even though we've agreed that the validation stuff needs to be removed, why waste time keeping this issue open when it will just be won't fixed in a week? Waste of time.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Category: task » bug

We have agreed to delegate part of the tasks executed from XML sitemap engines to an independent project when the other project will be ready for an official release, and (I add it now) its user interface will be changed.

There is no waste time with an open issue; or at least I am not wasting any time on this.

Actually, this report should be a bug report; the absence of validation is quietly a bug of the code.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Postponed

I am setting this report as postponed, waiting that another task gets completed (see #464980: Remove search engine authentication/verification code, which is postponed because of #467582: Change the settings page).

Anonymous’s picture

Anonymous (not verified) commented
Status: Postponed » Closed (won't fix)

As Dave said in #1.