[closed] [orphaned] "delete account" button missing

Mathilde

Could you clarify please that there are only valid bugs for your flagship instance?
I was not given these steps on the bug, it was closed immediately.

I see this post which answers:

Nope, it's likely an instance configuration or a client issue from your end. We don't do community support on GitHub, as you have read on the bug report template it's for reproducible bugs only.

However, you did well to reach out on the community forum, it's where that kind of issue (which isn't a bug) gets sorted out. See you there.

We can move on from the handling of that bug to the issue at hand.
If it is found to be an actual bug, I would encourage asking more questions than simply closing, but let's forget about it.

The checkup reports (erroneously) that encrypted support ticket functionality has not been enabled., yet it is enabled; so this checkup is broken and all tests pass.

It does note that I have customized a few options in application_config.js, however none of these options should disable the delete account button.

// SPDX-FileCopyrightText: 2023 XWiki CryptPad Team <contact@cryptpad.org> and contributors
//
// SPDX-License-Identifier: AGPL-3.0-or-later

/*
 * You can override the configurable values from this file.
 * The recommended method is to make a copy of this file (/customize.dist/application_config.js)
   in a 'customize' directory (/customize/application_config.js).
 * If you want to check all the configurable values, you can open the internal configuration file
   but you should not change it directly (/common/application_config_internal.js)
*/
define(['/common/application_config_internal.js'], function (AppConfig) {
    // Example: If you want to remove the survey link in the menu:
    // AppConfig.surveyURL = "";

    // To inform users of the support ticket panel which languages your admins speak:
    //AppConfig.supportLanguages = [ 'en', 'fr' ];
    // Prevent anonymous users from storing pads in their drive
    // NOTE: this is only enforced client-side as the server does not distinguish between users drives and pads
    AppConfig.disableAnonymousStore = true;
    // Prevent anonymous users from creating new pads (they can still access and edit existing ones)
    // NOTE: this is only enforced client-side and will not prevent malicious clients from storing data
    AppConfig.disableAnonymousPadCreation = true;

    // Disable feedback for all the users and hide the settings part about feedback
    AppConfig.disableFeedback = true;
    return AppConfig;
});

In this photo you can see there is no delete button, neither big nor red.

@Mathilde -- could you provide some further clarity on which configuration error I have made to break this functionality or re-open the bug with the necessary supplemental details which were missing to keep it open originally?

Mathilde

Understood, thanks for the context and apology! CryptPad has a great wealth of install base and I can understand your perspective.

I have re-read the common issues section you have linked. Could we go through the common issues section together?

• Check the list of extensions below, disable the ones you have installed, if any
  • None! I made sure to use a clean Chromium browser with no user configuration.
• Try using your browser in a private window and/or with all extensions disabled
  • Done! I made sure to use a clean Chromium browser with no user configuration, and repeated the login with incognito. I also repeated it with a standard user account on someone else's computer.
• Try using a different browser. We recommend the latest versions of Firefox or Chromium
  • Done! I don't daily drive Chromium; I use Firefox and that's where all my user configuration, extensions and etc. are. It originally presented itself in Firefox
• If the issues persist, please contact support
  • This is perhaps where I have gone wrong earlier. I filed a bug because there was no directions here on how to contact support. Is this forums support? I recommend providing a direct link here as to which method of contact counts as support.

Is there an email inbox I should take this bug to?