Hi all,

Tested both on local site upgraded from OA 2.44 to 2.45 and on a fresh standard install of OA 2.45 on Pantheon.

Issue:
On Site Map web page I noticed that (happens since at least OA 2.43), after creating a new Section through the Sitemap "+" New Section action, this new Section is visualized (circle icon) on the Site Map two times before the web page is manually refreshed (which shouldn't be necessary); this happens no matter if this new Section is the very first one or is added to others yet available on that Space and it is unrelated to the Type of Section chosen.
It looks like a cache issue on the web browser (or the lack of an automatic web page reload just after the action is submitted).

Notes:
The message "Section Page xxxxxx has been created." will appear only after the web page is manually reloaded.
The issue doesn't happen once the Site Map page is reloaded manually the first time.
After the Site Map web page reloads link to the new node (Section) is in the form /spacename/sectionname (e.g /backoffice/calendar), before the web reload link is in the form /node/nodenumber (e.g. /node/102)...but, in both cases, link works.

How to reproduce:

  1. As Admin (or other user with proper OG permissions/role rights) add a Space
  2. Add a Section with "+" New Section button
  3. Fill required information (select a Section Title, a Section Type - I tested all Section Types - and leave Section Visibility values default) and just Publish

Expected result:
Only one section icon will appear on the Site Map (before any web browsing reload of the page).

Obtained result:
Two Section icons will appear on the Site Map, both pointing to the same new Node (before any web browsing reload of the page).

If the Site Map web page if refreshed manually after that the expected result is obtained and Issue doesn't happen anymore.

Comments

dpoletto created an issue. See original summary.

dpoletto’s picture

Issue summary: View changes
mpotter’s picture

I think this was already reported somewhere. It's a known issue that we didn't get to for 2.45 and patches are always welcome.

dpoletto’s picture

Yep, maybe was me three days ago (despite, at time, visible Section Icons where even three and not only two!); for reference see at the end of this Comment.

mpotter’s picture

Status: Active » Fixed

Fixed in commit b2c4f06.

saqibmabbasi’s picture

Guys,
I'm new to Drupal and Open Atrium,
How can I access this patch, because this same problem is occurring on my Open Atrium "7.x-2.42" install, but in my case the number of Section icons were much more than two or three.

Thanks,

dpoletto’s picture

The Patch for this issue can be found looking here: http://cgit.drupalcode.org/oa_sitemap/ (the Commit is specifically described here and the Patch file is this one).

Looking at previous commits' release dates (latest batch was in August, so well before latest Commit you're interested in) I think (I could be wrong) that the Patch you're looking for was created against oa_sitemap 2.8 (which is available through latest Open Atrium 2.45 update and which should be the actual Head) so I'm not sure you can blindly apply the proposed patch directly against oa_sitemap 2.6 of your Open Atrium 2.42, at least if before you manually don't check what other differences were applied - as patches - between your oa_sitemap 2.6 and actual oa_sitemap 2.8 and patch them all up to the latest available to update your oa_sitemap to the version required by the latest patch itself.

IMHO you should *avoid* proceeding manually and wait to perform an update of your *whole* Open Atrium distribution from 2.42 to actual 2.45 or to 2.50 that, from what I've read in other Post's comments recently published, should be released soon.

saqibmabbasi’s picture

Okay thanks will check the impact and then first update to latest version of Open Atrium before I move forward with updating OA_Sitemap

dpoletto’s picture

Yep, properly updating your whole Open Atrium distribution to upcoming 2.50 shall incorporate the latest Open Atrium Sitemap version (probably its version would be named 2.9) with all the committed patches and the issue should disappear...so there is no need to act separately on that single module after the site update.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.