Major problem in DOCS after 1.04 CBox upgrade: Children docs URLs messed up…
Tagged: docs, Page pathways, tags
- This topic has 11 replies, 3 voices, and was last updated 11 years, 6 months ago by Helene Finidori.
-
AuthorPosts
-
May 25, 2013 at 10:09 am #2771Helene FinidoriParticipant
Hi,
We are experiencing a major problem with our docs after upgrade from Cbox 1.02 to 1.04. All the docs that have been created as children can’t be accessed on the wiki both as links and as children. This seems to be a redesign of the URL pathways
URL in the parent’s doc ‘children link’ : returning a page not found message:
And URL for viewing the page via Docs edit on the dashboard:
Both returning a page not found message…
URL as wiki link in parent page (the original link in the previous cbox version):
http://commonsabundance.net/wiki/complete-streets/
returning the following message:
On Firefox: The page isn’t redirecting properly Firefox has detected that the server is redirecting the request for this address in a way that will never complete. This problem can sometimes be caused by disabling or refusing to accept cookies.
On safari: too many redirects trying to open page xxx, this may occur if you open another page that is then redirected to open the original page…
As a result, half our wiki is inaccessible! And we are starting our official launch today…
May 25, 2013 at 11:58 am #2773Helene FinidoriParticipantAlso docs or wiki pages can’t be saved with a parent doc assigned. The same redirection messages as above appear…
May 27, 2013 at 12:22 pm #2788Helene FinidoriParticipantSeems there’s a confusion between wiki docs and regular docs in the upgrade… Seems the wiki pages (a special kind of docs created via a different process) are not recognized as such anymore…
May 27, 2013 at 12:42 pm #2789Wolfgang HoescheleParticipantI’d like to add to Helene’s post (since we’re both working together on this project), that checking on the dashboard, we could find that wiki docs are still there with the URL that they were originally given, and one can edit them from the dashboard. However, a normal user who has no access to the dashboard can’t access those documents! It means that half of our wiki has been disabled! We really need to get that going again, especially as we want to add more pages to the site.
We also did an experiment of creating a new page with an old name, and copying and pasting the content from the old page into the new one. This new page is now accessible to an ordinary user, but the content has now been doubled – you first read the new page, and then, as you scroll down, you get to the old page (because our parent and tag designations were different in the two pages, we could tell which is which). That doubled page is here: http://commonsabundance.net/docs/complete-streets/ (note that it now lists it as docs, not wiki as it did before).
This thing is really messing up our site!!!! We need some help here.
Wolfgang
May 27, 2013 at 2:48 pm #2791Boone GorgesKeymasterHi Helene and Wolfgang. There is a known issue where nested child docs do not resolve properly: https://github.com/boonebgorges/buddypress-docs/issues/308 Given the URLs that Helene cites above, I’m guessing this is the same issue you’re experiencing. While I look for a fix the nesting problem, could I ask you to do some experiments to verify whether it is indeed the same issue? That is, are you experiencing problem with *all* child docs, or only those that are children of other children?
May 27, 2013 at 3:45 pm #2792Wolfgang HoescheleParticipantHi Boone,
It seems to be a problem only with children of children.
We can access the main page we have constructed (Needs, Organizational forms and Resources for Abundance), and its children (e.g., air, water to drink, food, being at home etc.), but not the children of those children.
Thanks for looking into this!
Wolfgang
May 27, 2013 at 4:07 pm #2793Boone GorgesKeymasterI just released version 1.4.2 of BuddyPress Docs, which addresses (among other things) your nested Doc issue. Please download the plugin from http://wordpress.org/plugins/buddypress-docs/ and (using FTP or the Dashboard plugin uploader) replace your existing version of BuddyPress Docs with 1.4.2. I’ll release a version of Commons In A Box that points to the updated version of Docs, but it might not be for a few days because of the necessary testing. And please let me know whether it fixes your problem.
May 27, 2013 at 9:26 pm #2797Wolfgang HoescheleParticipantThank you,Boone, that worked.
We’re still encountering a different problem though, which is that the tags at the bottom of a page are not working properly – they just redirect to the top of the same page, instead of to a listing of pages with that tag. Is there a fix for that?
Thanks,
Wolfgang
May 28, 2013 at 7:34 am #2798Boone GorgesKeymasterWolfgang – What URL do the links point to?
May 28, 2013 at 7:43 am #2799Helene FinidoriParticipantTag links point to the following:
http://commonsabundance.net/wiki/land/?bpd_tag=property
From the land page back to the top of the land page and not the list of pages related to the property tag (same for all other tags on this page).
And while we are at it with fixes, Boone, comments are not displayed/available on docs to the type of users they have been enabled for at the doc creation/edition level…
May 28, 2013 at 1:44 pm #2801Boone GorgesKeymasterI’ve fixed the tag directory link issue: https://github.com/boonebgorges/buddypress-docs/commit/df4d30adc161abd7a15406c59727d4c1b8fcd1c3 You can apply it manually to your copy of BuddyPress Docs, or wait for the next version.
> comments are not displayed/available on docs to the type of users they have been enabled for at the doc creation/edition level…
I can’t reproduce this, at least not with this description. If you wouldn’t mind, please open a ticket at http://github.com/boonebgorges/buddypress-docs/issues with a description of your problem and detailed instructions on how I can reproduce. Thanks.
May 28, 2013 at 3:04 pm #2804Helene FinidoriParticipantFor comments: ticket opened on github.
@cbox_admin, I have myself tried to reproduce this issue on a doc on this instance of cbox here but couldn’t (i.e. everything worked fine). Though I wasn’t sure cbox 1.04 had been installed here, on this particular instance (i.e whether you are eating your own dogfood is what I do not know 😀 )
-
AuthorPosts
- You must be logged in to reply to this topic.