Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"(Default)" marker in Site Search interferes with reindexing #24176

Closed
jdcmsd opened this issue Feb 21, 2023 · 3 comments · Fixed by #25085
Closed

"(Default)" marker in Site Search interferes with reindexing #24176

jdcmsd opened this issue Feb 21, 2023 · 3 comments · Fixed by #25085
Assignees

Comments

@jdcmsd
Copy link
Contributor

jdcmsd commented Feb 21, 2023

Problem Statement

In the Alias Name input field under Dev Tools → Site Search → Job Scheduler, it notes which index is the default by adding (Default) to the end of it. However, this is treated as part of the input value, and furthermore contains invalid characters, resulting in this error on an attempted reindex of a default index:

Screenshot 2023-02-21 at 3 22 24 PM

This is solvable by manually deleting the "(Default)" text.

Steps to Reproduce

  1. On Demo, go to Dev Tools → Site Search.
  2. Create an index in either of the following ways:
    1. Under Indices, click Create Site Search Index and enter the name test
    2. Or: under Job Scheduler, set the following values:
      • Run: Now
      • Check the Index All Sites box
      • Select all languages
      • Enter the Alias Name test
  3. Now that you have an index, ensure it is set to the Default state.
    • If it is not the default, then under Indices, right-click it and pick Make default.
      Screenshot 2023-02-21 at 3 44 36 PM
  4. Go to Job Scheduler and enter the parameters given above: Run/Now, Index All Sites, all languages. However, leave the Alias Name field as it appears with the test (Default) text, or select it from the dropdown if it is not already present.
  5. Click Schedule, see error.
    Screenshot 2023-02-21 at 3 45 03 PM

After this, delete (Default) from the input, leaving just test, and then click Schedule again. The job should schedule properly.

Acceptance Criteria

We should accept the (Default) value.

dotCMS Version

Tested on 23.02, 22.09.

Proposed Objective

User Experience

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Sub-Tasks & Estimates

No response

@jdcmsd
Copy link
Contributor Author

jdcmsd commented Jun 9, 2023

If I'm understanding correctly, this solution should make it possible for the index to be saved with the (Default) it adds. But then the next time you run the job, wouldn't it list the index name as test(Default) (Default), and then test(Default)(Default) (Default), and so on?

@erickgonzalez
Copy link
Contributor

@jdcmsd No, the name is kept as test (Default)

@josemejias11
Copy link

Approved QA - Tested on master_86f6fb2b_SNAPSHOT // Docker // macOS 13.0 // FF v113.0

erickgonzalez added a commit that referenced this issue Aug 23, 2023
erickgonzalez added a commit that referenced this issue Aug 30, 2023
@erickgonzalez erickgonzalez added Release : 22.03.9 Included in LTS patch release 22.03.9 Release : 23.01.6 Included in LTS patch release 23.01.6 and removed Next LTS Release labels Sep 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

6 participants