On 29/06/17 19:55, Emmanuel Lécharny wrote:
Le 29/06/2017 à 11:03, Brian Burch a écrit :
Stefan has kindly helped me jump through several hurdles, so I
successfully committed a small change to the Advanced User Guide
(correcting invalid markdown for urls inside a table). I edited the
text and used svn to update the site source.
I can login to the staging directory and see my change has had the
expected effect, so now I want to publish it to the production site.
I have been very confused by the CMS "help" pages, but think I am
doing mostly the correct things.
I created a google chrome bookmark containing the cms bookmarklet. I
navigated to the updated page in the staging site. I activated the
bookmarklet while on the page and entered my credentials. I selected
the "publish" hyperlink and was taken to the publish page.
When I click the "diff" button, nothing happens and the request never
completes.
When I crossed my fingers and hit the "submit" button (after adding a
commit message", it took several minutes and eventually congratulated
me on my update. However, when I was taken to the public page it had
not been changed!
Actually, it did change :-)
The thing is that the public site might not be updated immediately, but
at a differed time (like every 30 minutes).
That is reassuring now that you have explained there is usually a delay.
So now, if you go to
http://directory.apache.org/apacheds/advanced-ug/4.2-authorization.html,
you can see your changes !
No I couldn't!!! I copied your url above into a new browser window and
the "bad" markdown was still there...
I was just about to tell you about the problem and I remembered the
browser might have cached the page (for 5 hours?)... so I did
shift/reload and was VERY relieved to see the hyperlinks were then
properly displayed... and they worked as originally intended.
Yes, I know, it's a bit complictaed, but it seems you successuly
navigated through the maze, thank you for that !Brian
p.s. Several apache projects actually put the recipe for their
specific web sites on their wiki, but those I looked at don't really
say anything different to the cms reference that I was trying to follow.
At this point, it might be useful for us to add a page explaining how to
update the web site...
As I said before, a few projects actually have their own procedures on
their sites, but apart from using their own specific urls, rather than
the generic information in the CMS guide, they don't add any value as
far as can see.
However, NONE of them mention the delay in the publish process - after
all it says something like "your publish was successful" (note the past
tense!). None of them mention the browser caching "gotcha", either.
If you don't think I am being too critical, I suppose it wouldn't take
long for me to clone a set of instructions (the CMS ones are pretty
opaque) and add a new page to the Directory wiki which points out these
issues before they fade from my memory. I'll try to do it in the next
week or so.
Many thanks Brian !
Oh, I don't need thanking. You all were so helpful recently that I see
it as just a small repayment to the project.
I have a few more details in mind, but my personal task list seems to
grow faster than I can deal with at the moment. It is just a pity my
2-line change chewed up so much time, otherwise I would have dome more
during this stint.
Thanks to the help from you and Stefan, I got there in the end.
Brian
