Project

General

Profile

Actions

Bug #13088

closed

Commons 1.17 creating group + site

Added by scott voth over 3 years ago. Updated over 3 years ago.

Status:
Rejected
Priority name:
Normal
Assignee:
Category name:
Site cloning
Target version:
Start date:
2020-07-26
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

In doing the documentation I notice issues with creating a group + site. If you are creating a new site, everything is fine, but when creating a group and an existing site or when cloning a site, it seems that the radio buttons are not displaying the correct pathways.


Files

clone site.png (436 KB) clone site.png scott voth, 2020-07-26 03:27 PM
existing site.png (398 KB) existing site.png scott voth, 2020-07-26 03:28 PM
1.17.0-group-clone-existing-site.png (274 KB) 1.17.0-group-clone-existing-site.png Jeremy Felt, 2020-07-26 09:32 PM
1.17.0-group-connect-existing-site.png (448 KB) 1.17.0-group-connect-existing-site.png Jeremy Felt, 2020-07-26 09:32 PM
Actions #1

Updated by Boone Gorges over 3 years ago

  • Target version set to 1.17.0

Scott, could you please provide screenshots or more details that spell out "radio buttons are not displaying the correct pathways"?

Jeremy, if you can't get to this by midday on Monday, I'll hop in and take a look. Would be nice to clear it up before the Tuesday release.

Actions #2

Updated by scott voth over 3 years ago

see pathways attached

Actions #3

Updated by Jeremy Felt over 3 years ago


I'll have some time tomorrow morning to adjust things as needed. I don't think anything should be that far off to require a bunch of work.

Scott - I've attached the screens that I see when I go through the process. Can you expand on which radio buttons or sections seem off?

Actions #4

Updated by Boone Gorges over 3 years ago

Just a guess, but it could be that something's triggering a JS error elsewhere on the page, causing the radio button click callback not to be fired. Scott, if you get a chance, please share details on your OS/browser. Also, if you could open your JS console and reproduce your error, then look to see if there are errors in the console.

Actions #5

Updated by scott voth over 3 years ago

Hi - What I did was clear the cache and now it seems to work fine. Sorry for the alarm.

Actions #6

Updated by Boone Gorges over 3 years ago

  • Status changed from New to Rejected

No need for apologies, Scott - the best bugs are the ones that aren't :-D

Actions

Also available in: Atom PDF