Hi!
I just added some translations for the search form that Phil added and
made a small fix so that swish.py now correctly ignores the # lines that
are output by search++.
bye, Georg
Hi!
> I've just made a couple of quick changes:
Cool, I hoped you would do that, at least the authorizer.py part ;-)
bye, Georg
I've just made a couple of quick changes:
- swish.py now displays a search box if no query string is entered
- authorizer.py now covers searches (so access to swish.py is governed by
the same rules as comments.py and mailto.py - i.e. the same as access to the
blog) ...
Cheers,
Phil :)
> Just a quick and dirty hack: modules/system/swish.py and make_index.sh
> give
> you the ability to set up per-user search indexes and search them using
> swish++ via a simple web form.
Great!
I'm still struggling on getting ht://Dig in ... it's been quite painful. I
hate autoconf/automake ;-)
(progress: I've turned ht://dig into a Python module, but it doesn't know
where its dependencies - a whole load of shared libs - are located, so
importing fails unless you set LD_LIBRARY_PATH.)
I'll plug this one in for the meantime - thanks for hacking it up!
Phil
> Now, i should also mention that because i'm doing all this on windows, i
> could not run the makefile, so i've had to manually create all the
> directories and put all the file where they should go (reading a makefile
is
> a bit of a pain! ;). One thing that i noticed is that the weblogUpdate.py
> file is not in the /system directory in the .gz download file - i had to
> manually move the weblogUpdate.py file to the system dir. In the /system
dir
> is only 'update.py'... Not sure if that has anything to do with it, but
this
> always fails when it follows the 'recently updated' link which points to
the
> weblogUpdate.py script.
Aha - here's what you need to do:
- use the version from CVS rather than the .gz file, which is probably
horribly out of date. As well as having loads of new features, it's
probably heaps more stable ;)
- there _is_ a weblogUpdates.py in the /system directory; it's just that
there's _another_ one in the root. That's where they're meant to be: the
one in the root is the handler for the weblogUpdates XML-RPC call (that's
the one that puts you on the updates page), and the one in /system is the
updates page itself.
If you check out the archive and copy both of those into the right places,
then restart, you'll probably find that your weblog updates will work again.
Actually, now that I think about it, it used to work on Windows if you just
extracted everything into a directory and ran from there. You certainly
don't need to copy everything into /var/lib/pycs and stuff. Read
pycs_paths.py though - it should have some details about where things go on
Windows, which is a bit simpler than on Linux. (This is one of the things
that is probably different in CVS and in the .gz on SourceForge).
Cheers,
Phil :)
Hi!
Because of the fact that there are now search terms that lead from google
directly to my zeitgeist.py, I thought about disabling this google bomb
and
added a way to prevent robot indexing of pages in the PyCS. I enabled
this
in the named three modules, so output of those are not indexed, not
followed
and not archived in google and other well behaving robots.
The problem is, my zeitgeist.py is a page that is a) heavily linked from
my
weblog and b) links to many pages outside, so google gives it quite a
high
rank. Adding to this, there are now popping up search hits that actually
only point to my page. This is fun (search-engine created art, so to
say), but
actually not really that usefull if those pages clogg up searchspace ;-)
bye, Georg
Hi!
Just a quick and dirty hack: modules/system/swish.py and make_index.sh
give
you the ability to set up per-user search indexes and search them using
swish++ via a simple web form.
http://muensterland.org/system/swish.py?usernum=1&q=Contax
searches on my main weblog for all Contax related pages. It's really very
crude and simple, just enough to set up searches. Hopefully I escaped the
search string correctly, so it won't create a security risk. I made sure
that
only a subset of allowed chars is in the query, so it usually shouldn't
make problems.
bye, Georg
Hi!
On Fri, Feb 28, 2003 at 10:18:01AM -0500, digital hyakugei wrote:
> I've got pyDS running. I (sort of) have it talking to pycs.net
Hey, that is cool, as I never ever tried it with W2K :-)
> (http://www.pycs.net/users/0000074/) tho phil said that it wasn't really
> talking to pycs correctly - could be - the pyDS docs leave a bit to be
Hmm. Looks fine to me, except that several files are missing (images and
stylesheet). This might be due to the fact that PyDS isn't really
Window-aware and needs a $HOME directory for the user and want's to
create a .PyDS directory there and populate it. So all this might go bad
on Windows, as there isn't such a thing like users home directories and
hidden directories in the Unix sense.
Did you set a HOME environment variable to point to some place where
your current user has write permissions?
Oh, and you created a user at muensterland.org, too. But I assume that
was because some experiments, right? Doesn't look too populated, that
directory ;-)
> desired ;). In the upstream pref i think i used the url:
> http://www.pycs.net/RPC2... Thats about it.
Yep, you usually don't need to do more. Everything else comes from the
community server.
> <error>
> Traceback (most recent call last):
> File "pycs_module_handler.py", line 155, in continue_request
> mod = cached_module( realPath )
> File "pycs_module_handler.py", line 78, in __init__
> self.Recompile()
> File "pycs_module_handler.py", line 86, in Recompile
> self.module = compile(code,self.path,'exec')
> File "<string>", line 116
>
> SyntaxError: invalid syntax
> </error>
What is in line 116 of weblogUpdates.py on your machine? Maybe there is
just a broken version in the tar.gz? I never installed it that way, as I
always use CVS :-)
> I also had another question about pyCS - is there any chance that it will
> speak the blogger API? does this request even make sense? I've looked into
No, PyCS can't speak it, as it isn't a weblog application but a
community server. The blogger API should go into PyDS, as that is the
desktop part of the bunch. But I currently don't work on it.
> Radio and know what it does, but i'm a bit unclear about RCS/pyCS's function
> and if it/they require a client like Radio/pyDS...
RCS/pyCS are just the server that pushes out your static content, you
generated with Radio or PyDS or bzero. A community server has several
aspects and functions:
- user registration (mostly done automatic) for new users
- uploading of changed files
- pushing static files to the world
- comment functionality
- referer, searches or other reports
So it is a bit like an FTP server with some CGI functionality, if you
want to see it like that.
bye, Georg
Hello all.
I sent an email to Phillip Pearson who was kind enough to get back to me and
point me here - so, let me give you the low-down on what i've managed to do
so far.
I've got a win2k box. Running python 2.2
I've got pyDS running. I (sort of) have it talking to pycs.net
(http://www.pycs.net/users/0000074/) tho phil said that it wasn't really
talking to pycs correctly - could be - the pyDS docs leave a bit to be
desired ;). In the upstream pref i think i used the url:
http://www.pycs.net/RPC2... Thats about it.
I got pyCS going locally (after a fair bit of futzing with PIL). However!!!
I get the following error when i try to access the 'recently updated' link
off the default main page:
<error>
Traceback (most recent call last):
File "pycs_module_handler.py", line 155, in continue_request
mod = cached_module( realPath )
File "pycs_module_handler.py", line 78, in __init__
self.Recompile()
File "pycs_module_handler.py", line 86, in Recompile
self.module = compile(code,self.path,'exec')
File "<string>", line 116
SyntaxError: invalid syntax
</error>
Now, i should also mention that because i'm doing all this on windows, i
could not run the makefile, so i've had to manually create all the
directories and put all the file where they should go (reading a makefile is
a bit of a pain! ;). One thing that i noticed is that the weblogUpdate.py
file is not in the /system directory in the .gz download file - i had to
manually move the weblogUpdate.py file to the system dir. In the /system dir
is only 'update.py'... Not sure if that has anything to do with it, but this
always fails when it follows the 'recently updated' link which points to the
weblogUpdate.py script.
I also had another question about pyCS - is there any chance that it will
speak the blogger API? does this request even make sense? I've looked into
Radio and know what it does, but i'm a bit unclear about RCS/pyCS's function
and if it/they require a client like Radio/pyDS...
Thanks very much,
jos