> >
> > I've been reading and trying to follow just how the RCS works in Nadmin
> > since I need to do similar things in a custom interface (Nadmin won't
> > do, too many steps for a simple update, users get confused),
> > unfortunately I quite can't follow it. I've been looking at the code
> > snippets (rcs_functions, edit_functions and edit) but they refuse to
> > open their secrets to me.
> 
> the rcs write function should  for every update
> 
> define a filename =  SGnumber+type+id
> they then call co - to check out the file (if it exists)
> 
>  write the contents of the object (eg. body text + some header info) to the
> file
> 
> then ci - to check in the new code
> 
> the diff code is based around webcvs I think.. - i didnt write that be..
> 
> the file name should really have been the GUID - but the code was written
> before that came out..
> 
> this stuff is wrapped up in functions which usually just recieve the filename
> and the contents and do all the ci/co stuff..
> 

Ok, I'll look into it with this info tomorrow (and propably come back
whining that I still can't figure it out ;)

Luckily I don't need to manage diffs or going back revisions with the
simplified system, those can be done trough Nadmin when needed but for
that I need the revision history to be present...

> >
> > Luckily I managed to find the source of the feature that images are
> > never attached to articles but to the parent topics instead and change
> > it to work the way I wanted it (ie. images are attached to articles when
> > article is selected), that wasn't too easy either, btw.
> 
> That should be quite easy - you may have to see if the image upload supports
> the mgd_get_article before attaching it to one...
> 

The change was easily made and seems to work like charm (I haven't done
too extensive testing yet), however it took a bit of detective work to
find where the actual code that defined where the attachment belongs
resided.

The insides of Nadmin are more complex to navigate than I at first
thought they would be.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to