MarieDi

@carike
Thank you so much for this complete and explanatory answer.
Duly noted, on all counts.
I wasn’t aware of Core Trac or WP Tavern. All I knew about was github which is way beyond my tech comfort zone ??
Have a great day!

The basic sitemaps feature has no UI or settings because it doesn’t need one. I’m sure plugins will exist soon enough to let people customize them and adjust them and so on, but by and large, most users should not care about sitemaps. It’s not relevant to them.

That’s your opinion. I beg to differ. You talk like a true coder, not a user. Drupal never became very popular because it is for coders, not for users. Joomla was becoming popular until it veered towards coders. WordPress did become popular because it used to be for users, not for coders. Something that, sometimes, seems to be slowly slipping away.

On many of my sites, I create categories I DO NOT want the public to see because they are for internal management. I create articles and pages that are private/reserved for certain users.
The sitemap discloses everything.

And if the User ID isn’t a [small] part of security, then explain to me why we instruct everyone to NEVER use “Admin” as a User ID.

But hey, I was only voicing a user’s point of view. So thank you, but I’m afraid we’re not seeing eye to eye here and I don’t see the point of continuing this discussion with you if you don’t want to hear my point (which, I guess, is your right).

@carike I didn’t mean to be discourteous to anyone and I thank everyone who answered.
However, this forum is the only place where we can voice to WordPress our concerns and issues.

Suggesting to use Yoast or any other sitemap plugin is ok, but suggesting to check the “do not index this site” option is not a viable solution for any site whatsoever except during it’s development phase. That cannot be a serious suggestion for a solution.

So let me be clear. I firmly believe this update, just like the completely premature Gutenberg implementation, has been done without thinking of the ordinary end-user (who I’m guessing would be about 85% of users?) who is using WP specifically BECAUSE you don’t have to code.

Implementing a sitemap that discloses User IDs and all posts/pages without ANY control whatsoever is a ridiculous move. One that makes me look for another solution that wordpress because with over 80 installs to supervise, it is a nightmare, whatever solution I try to implement.

I just can’t understand why this has been implemented without a UI and optional settings. And if no one complains, it will never be fixed. So I voice my complaint. And I know I’m not the only one. Hopefully someone will step in and include in the core a UI so we can choose sitemap settings instead of having to either code or add yet another plugin.

• This reply was modified 4 years, 7 months ago by MarieDi.

@sterndata

First, I don’t use Yoast and don’t plan to. Second… Are you serious? You are actually telling me to hide my sites from search engines? Seriously?
Maybe a DECENT core sitemap would have been in order before you enforced it on all of us without warning?

@pbiron

I strongly disagree with you.

My themes NEVER show authors archives, and the core WP sitemap shows actual user IDs. I manage too many sites to go and manually change all of this.

This sitemap is horrible.

@otto42 and @carike, thanks, but this should have been thought out before WP rolled out a sitemap without settings. Access is made of UserID + Password. So User ID IS part of the security and removing it is bad. I have sites that are regularly under attack and the first thing they try to find is the User ID. So by default I install the Stop User Enumaration plugin to make it a bit more difficult for them. Now just asking for the sitemap will give a 4 y.o. access to all the User IDs.

@pidengmor, @otto42 and @carike: I’m NOT a coder. I DON’T WANT to touch code. MOST WP USERS use WP specifically BECAUSE they don’t have to touch code. And now v.5.5 has been rolled out WITHOUT ANY sitemap UI/settings except for coding. Even the instruction page you sent me to @pidengmor (thanks for that, it’s a good reference), assumes that I know WHERE to go for those codes. I don’t. MOST users don’t. Someone, somewhere, forgot that, apparently.

I agree 100% with you, but there is worse. The new sitemap actually discloses ALL authors’ user IDs.

It certainly does clarify that small non profits are at a loss here. But hey, it’s your business.

You force non-profits and educational organizations to pay?
I have always removed Akismet since I started doing WP sites in 2010, but I was actually considering using it now for a non-profit. I never imagined you would charge a non profit. So, I’ll be back to my old habit of deleting it.

And for the record, I agree that it should NOT be bundled with WP because there are now many other solutions to control spam.

My pleasure!

@prasunsen, I think I know. I struggled with this in the beginning.

When you create questions, they are “ID-numbered” (each question has a unique ID-number).
When you create a quizz, every question in it is order-numbered (you can reorganize the order and the order-number changes).

When you erase/delete a question, it’s ID-number disappears and is not recycled.

However, the way it is implemented, when you are CREATING quizzes, the ID-numbers look like order-numbers, and when you delete a question, so you end up with ID-numbers that do not exist anymore and if you still confuse ID-numbers with order-numbers, you’re in for a lot of fun.

So @gerardphilippe: that is your answer.
Each question has a UNIQUE ID-number that cannot be recycled because it is used by the software to identify it uniquely.
Each question in a quizz has an order-number that reflects its position in the quizz. When yo reorder questions in a quizz, each question’s order number might change, but it’s ID-number will never change.
When you delete a question, it’s ID-number disappears altogether. It will NOT be recycled.
If you don’t like it, then instead of deleting questions, modify them. ??

Look at the top of your questions list in the quizz (questions management, not the actual front-end quizz) and you will see:
A check box “title”/ a “#” title / an “ID” title
the # title column is for the question order number within any given quizz (changeable)
the ID column gives you the unique ID-number of each question.

NB: if you Duplicate a question, the duplicate is given a different ID-number.

Hope this helps.

Marie

• This reply was modified 6 years, 3 months ago by MarieDi.
• This reply was modified 6 years, 3 months ago by MarieDi. Reason: typos

Let me specify and clarify: there has been nothing personal. Of course “You” designated whoever is making decisions about WP and Gutenberg. It did not designate any one person in particular.

The dashboard is warning everyone that the new version will have Gutenberg as default and warns that if we don’t want it we need to install Classic.
What I’m saying is PLEASE do not release Gutenberg until it is done. And right now it is NOT.
75% of negative reviews should send SOME message, no?
If it were done by anyone else, it would be on page 150 of the repository.

I just don’t understand why Gutenberg developers don’t seem to be aware of how much people DO NOT want it as it is now.

Anyway you seem to have decided I’m wrong, so it’s ok, I’ll be wrong with the other 75% reviewers of the beta Gutenberg plugin.

You could add an image block before the paragraph and then align it left or right as you need it.

I don’t want it before or after. I want it surrounded by text LIKE WE HAVE NOW IN pre-Gutenberg. You are taking away features instead of adding!

It is incomprehensible to me that you would remove features. We are at present able to have images WITHIN paragraphs (was I not clear that this what is missing?).

Moreover even the stupidest page builder allows for many blocks on the same line (columns) and we can achieve that with shortcodes. Now Gutenberg, PRETENDING to be based on blocks, REMOVES that possibility. What gives?

Maybe you want to give it another swirl with above suggestions and see how that works for you. It’s a learning curve for sure.

This is NOT my first try of Gutenberg. I tried it in April when it was supposed to be launched in June. NO GO. I tried it again now because you are threatening to roll out WP 5.0 with Gutenberg ACTIVE BY DEFAULT, and we are forced to install (yet another) plugin to stay clear of Gutenberg and not break our sites.

Gutenberg is and remains the WORST implementation of what could have been a brilliant idea. IT IS NOT.

75 % of those who tried Gutenberg agree with me. The list of complaints, the shear number of 1/5 stars is eloquent enough. SO WHY are you so deaf and blind??????

If you roll this crap out, you will kill WordPress for sure. I’m not the only one looking for other solutions right now because no one seems to be ready to admit this project STILL NEEDS AT LEAST TWO YEARS of INTELLIGENT development before it can be rolled out safely.

You are destroying a jewel of a platform.

And thinking that I haven’t tried it, that I don’t understand how it works, doesn’t help. It shows the little respect you have for users. Even seasoned users such as myself. I run at present about 30 WordPress websites. So yes, all this, your attitude included, is freaking me out.

‘Nough said.

Thank you so much. Very clear! ??

Thank you so much! That is exactly what I was looking for.
Can you tell me what “pad_counts” stands for?

Here is what the log says (partial only, of course):
ARCHIVE RUNTIME: 14.78 sec.
INTEGRITY CHECKS:
********************************************************************************
SQL File: 2.12MB
Installer File: 430.98KB
Archive File: 84.11MB

The log (and reality) says everything went smoothly. Only the plugin seems to think the archive has not been created when it has.