[LON-CAPA-users] publishing questions
Travis Souza
lon-capa-users@mail.lon-capa.org
Thu, 23 Jan 2003 13:43:37 -0800
This is a MIME message. If you are reading this text, you may want to
consider changing to a mail reader or gateway that understands how to
properly handle MIME multipart messages.
--=_356A3631.CCADC61E
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Thanks Gerd.
After all of this, I still have problems because the default.meta is
not read if there is an existing .meta for a resource. I can get around
this one by by deleting the individual .meta so that default.meta is the
only one left in the directory. I know that's probably a no-no too, but
we may want to think about an option to force a directory to use the
default.meta over any existing.
The moral of the story is to get it right the first time.
Travis
Travis Souza, Coordinator
Instructional Center for Innovation
Truckee Meadows Community College
775-674-7505
tsouza@tmcc.edu
>>> korte@lite.msu.edu 01/23/03 12:36PM >>>
Hi Travis,
Yes, since the files did not change, the publication skips them. Hmm
...
let me think about that one ...
But since you have been going in ssh anyway (usually not recommended
...), as user souza:
[/home/souza]$ cp -R public_html/* tmp
[/home/souza]$ mv public_html backup
[/home/souza]$ mv tmp public_html
Now as root:
[/home/souza]# chown -R www:souza public_html
If that works, you can remove /home/souza/backup
- Gerd.
Travis Souza wrote:
>
> >>> korte@lite.msu.edu 01/23/03 11:21AM >>>
>
>
> Gerd Kortemeyer wrote:
>
> >
> >
> > Travis Souza wrote:
> >
> > > Is there a way I can force the directories to re-publish
> > > using the default.meta?
> >
> > You can edit the "default.meta" with teh "Directory Catalog
> Information"
> > button. What you type there applies to the directory and all
> subdirs.
>
> ... after saving the info, you will need to press "Publish Directory
> and Sub
> Directories". Hi Gerd,I edited the default.meta after I published
the
> first time. When I tried to republish the directory it skips all of
> the files because they have not changed. I know that I can fix them
> individually but there are quite a few files. When I republish and
> individual resource it is updated with the contents of
> default.meta. Thanks. P.S. I also screwed up after failing to
> republish and moved some files around through ssh and messed up the
> permissions. I am getting errors when I try to publish from
> directories that I modified saying 'no write pemission to
directory'.
> It looks like I need to chown the directories to www:souza as the
> problem areas seem to be set as souza:souza. Am I hosed?
>
>
>
>
>
>
>
>
>
>
>
> >
> >
> > > Also when publishing from directories there
> > > seems to be no way to limit the scope of the resources to domain
> only.
> >
> > In "Directory Catalog Information", type the word "domain" under
> > "copyright".
>
> Again, make sure to re-publish.
>
> _______________________________________________
> LON-CAPA-users mailing list
> LON-CAPA-users@mail.lon-capa.org
> http://mail.lon-capa.org/mailman/listinfo/lon-capa-users Travis
Souza,
> Coordinator
> Instructional Center for Innovation
> Truckee Meadows Community College
> 775-674-7505
> tsouza@tmcc.edu
_______________________________________________
LON-CAPA-users mailing list
LON-CAPA-users@mail.lon-capa.org
http://mail.lon-capa.org/mailman/listinfo/lon-capa-users
--=_356A3631.CCADC61E
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Content-Description: HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4922.900" name=GENERATOR></HEAD>
<BODY style="MARGIN-TOP: 2px; FONT: 8pt Tahoma; MARGIN-LEFT: 2px">
<DIV><FONT size=2></FONT>Thanks Gerd.</DIV>
<DIV> </DIV>
<DIV>After all of this, I still have problems because the default.meta is not
read if there is an existing .meta for a resource. I can get around this
one by by deleting the individual .meta so that default.meta is the only one
left in the directory. I know that's probably a no-no too, but we may want
to think about an option to force a directory to use the default.meta over any
existing.</DIV>
<DIV> </DIV>
<DIV>The moral of the story is to get it right the first time.</DIV>
<DIV> </DIV>
<DIV>Travis</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Travis Souza, Coordinator<BR>Instructional Center for Innovation<BR>Truckee
Meadows Community College<BR>775-674-7505<BR><A
href="mailto:tsouza@tmcc.edu">tsouza@tmcc.edu</A> <BR><BR>>>>
korte@lite.msu.edu 01/23/03 12:36PM >>><BR>Hi Travis,<BR><BR>Yes, since
the files did not change, the publication skips them. Hmm ...<BR>let me think
about that one ...<BR><BR>But since you have been going in ssh anyway (usually
not recommended<BR>...), as user souza:<BR><BR>[/home/souza]$ cp -R
public_html/* tmp<BR>[/home/souza]$ mv public_html backup<BR>[/home/souza]$ mv
tmp public_html<BR><BR>Now as root:<BR><BR>[/home/souza]# chown -R www:souza
public_html<BR><BR>If that works, you can remove /home/souza/backup<BR><BR>-
Gerd.<BR><BR>Travis Souza wrote:<BR><BR>><BR>> >>>
korte@lite.msu.edu 01/23/03 11:21AM >>><BR>><BR>><BR>> Gerd
Kortemeyer wrote:<BR>><BR>> ><BR>> ><BR>> > Travis Souza
wrote:<BR>> ><BR>> > > Is there a way I can force the directories
to re-publish<BR>> > > using the default.meta?<BR>> ><BR>>
> You can edit the "default.meta" with teh "Directory Catalog<BR>>
Information"<BR>> > button. What you type there applies to the directory
and all<BR>> subdirs.<BR>><BR>> ... after saving the info, you will
need to press "Publish Directory<BR>> and Sub<BR>> Directories". Hi
Gerd,I edited the default.meta after I published the<BR>> first time.
When I tried to republish the directory it skips all of<BR>> the files
because they have not changed. I know that I can fix them<BR>>
individually but there are quite a few files. When I republish and<BR>>
individual resource it is updated with the contents of<BR>> default.meta.
Thanks. P.S. I also screwed up after failing to<BR>> republish and moved some
files around through ssh and messed up the<BR>> permissions. I am
getting errors when I try to publish from<BR>> directories that I modified
saying 'no write pemission to directory'.<BR>> It looks like I need to chown
the directories to www:souza as the<BR>> problem areas seem to be set as
souza:souza. Am I
hosed?<BR>><BR>><BR>><BR>><BR>><BR>><BR>><BR>><BR>><BR>><BR>><BR>>
><BR>> ><BR>> > > Also when publishing from directories
there<BR>> > > seems to be no way to limit the scope of the resources
to domain<BR>> only.<BR>> ><BR>> > In "Directory Catalog
Information", type the word "domain" under<BR>> >
"copyright".<BR>><BR>> Again, make sure to re-publish.<BR>><BR>>
_______________________________________________<BR>> LON-CAPA-users mailing
list<BR>> LON-CAPA-users@mail.lon-capa.org<BR>> <A
href="http://mail.lon-capa.org/mailman/listinfo/lon-capa-users">http://mail.lon-capa.org/mailman/listinfo/lon-capa-users</A>
Travis Souza,<BR>> Coordinator<BR>> Instructional Center for
Innovation<BR>> Truckee Meadows Community College<BR>>
775-674-7505<BR>>
tsouza@tmcc.edu<BR><BR>_______________________________________________<BR>LON-CAPA-users
mailing list<BR>LON-CAPA-users@mail.lon-capa.org<BR><A
href="http://mail.lon-capa.org/mailman/listinfo/lon-capa-users">http://mail.lon-capa.org/mailman/listinfo/lon-capa-users</A><BR></DIV></BODY></HTML>
--=_356A3631.CCADC61E--