Re: [campsite-dev] Search Problem - Newscoop Development Discussions on Sourcefabric Forum

import

Please use the "Select search level" statement.

http://code.campware.org/manuals/campsite/2.5/index.php?id=106

Example:

...

Search in:

...

This will display a popup list that allows the reader to restrict the search to:
- the whole publication (all issues)
- the current issue
- the current section

If you don't want to allow readers to select the search level and you want it to be set to "issue" then insert the following field inside the statement:

Set the value to:
- 0 for publication
- 1 for issue
- 2 for section

Regards,
Mugur

wrote: Author: fadez
Link: http://code.campware.org/phorum/read.php?9,4237,4237#msg-4237
--------------------------------------------------------------------------------

I have a multiple issues in a website and i want to make search for each issues

I have put the following form to search just for issue 2 and is not working , it listing articles in all issues not in issue 2

There is solution for that.

Best Regards

--
Sent from Campware Forums
http://code.campware.org/phorum

---------------------------------
Do you Yahoo!?
Next-gen email? Have it all with the all-new Yahoo! Mail Beta.

import

Mainly to Mugur and Paul,

I have to change phpwrapper/modules to work with short paths.
phpwrapper/modules will be a package with some modules like
poll/voting/timer, using Smarty template engine.

Here some thoughts about the implementation.

For the frontend I have to change existing phpwrapper scripts to work well
with shorts names url mode. As far I understood this mode works following
way:

1. Browser request is directed to index.php
2. index.php creates XML message out of apache parameters using
camp_create_url_request_message()
3. XML message is send to parser using camp_send_message_to_parser()
4. parser output will be read from socket and directed to browser using
camp_read_parser_output()

Am I right on this?

In my view it would make sence to "inject" phpwrapper mechanism in step 4,
this would mnake an internal http-connection obsolete in case of short
paths. Request parameters can still be taken from $_REQUEST (hope this array
will never be changed by index.php and relevant scripts).

For backend i will, as far it's possible, use the API decriped in
http://code.campware.org/api/campsite-2.6/. Have seen there is already a
ModuleConfiguration class, would this be helpful?
Also I have see Phorum related classes, how do you plan to integrate the
phorum?

phpwrapper/modules used own capsulation of instructions, which lokked like
. Should I change to ? This would need that the
parser let those markers passing by to the phpwrapper. Also it would make
sence that the parser avoid passing those markers in content (e.g. xhina
stores them as html-encoded), so code can just be in templates, not in
content.

Thanks for comments,
Sebastian

import

> 1. Browser request is directed to index.php
> 2. index.php creates XML message out of apache
> parameters using camp_create_url_request_message()
> 3. XML message is send to parser using
> camp_send_message_to_parser()
> 4. parser output will be read from socket and directed to
> browser using camp_read_parser_output()
> Am I right on this?
Yes

> In my view it would make sence to "inject" phpwrapper
> mechanism in step 4, this would mnake an internal
> http-connection obsolete in case of short paths.
OK so far

> Request parameters can still be taken from $_REQUEST
> (hope this array will never be changed by index.php and
> relevant scripts).
No, use the global variable $parameters (see line 29 in index.php). index.php is called from the cgi script also and in that case $_REQUEST variable doesn't exist.

> Have seen there is already a
> ModuleConfiguration class, would this be helpful?
It may be in case you want to create and manipulate your own configuration files.

> Also I have see Phorum related classes, how do you plan
> to integrate the phorum?
These classes are just wrappers around phorum API; these classes allow us to use the phorum for article comments and are very specific for this purpose, I don't think you can reuse them.

Please do not change the phorum markers to Campsite stile: . The template languages (Campsite and phorum) are quite different and it would take some work to modify the Campsite template engine to ignore yours.

Mugur

Sebastian Goebel wrote: Mainly to Mugur and Paul,

I have to change phpwrapper/modules to work with short paths.
phpwrapper/modules will be a package with some modules like
poll/voting/timer, using Smarty template engine.

Here some thoughts about the implementation.

For the frontend I have to change existing phpwrapper scripts to work well
with shorts names url mode. As far I understood this mode works following
way:

1. Browser request is directed to index.php
2. index.php creates XML message out of apache parameters using
camp_create_url_request_message()
3. XML message is send to parser using camp_send_message_to_parser()
4. parser output will be read from socket and directed to browser using
camp_read_parser_output()

Am I right on this?

In my view it would make sence to "inject" phpwrapper mechanism in step 4,
this would mnake an internal http-connection obsolete in case of short
paths. Request parameters can still be taken from $_REQUEST (hope this array
will never be changed by index.php and relevant scripts).

For backend i will, as far it's possible, use the API decriped in
http://code.campware.org/api/campsite-2.6/. Have seen there is already a
ModuleConfiguration class, would this be helpful?
Also I have see Phorum related classes, how do you plan to integrate the
phorum?

phpwrapper/modules used own capsulation of instructions, which lokked like
. Should I change to ? This would need that the
parser let those markers passing by to the phpwrapper. Also it would make
sence that the parser avoid passing those markers in content (e.g. xhina
stores them as html-encoded), so code can just be in templates, not in
content.

Thanks for comments,
Sebastian

---------------------------------
Yahoo! Music Unlimited - Access over 1 million songs.Try it free.

import

On http://code.campware.org/projects/campsite/wiki/CodingStandards
there is written:
1. Use a tab of four (4) characters, and set your editor to insert spaces
instead of tabs.

But it seems all php script use tab instead of spaces. What should I use?

Sebastian

import

this was taken from the PEAR standards (so there must be a lot of php
code using spaces Smile

http://pear.php.net/manual/en/standards.php
Indenting and Line
LengthUse an indent of 4
spaces, with no tabs. If you use Emacs to edit PEAR code, you should set
indent-tabs-mode to nil. Here is an example mode hook that will set up
Emacs according to these guidelines (you will need to ensure that it is
called when you are editing PHP files):
(defun php-mode-hook ()
(setq tab-width 4
        c-basic-offset 4
        c-hanging-comment-ender-p nil
        indent-tabs-mode
(not
    (and (string-match "/\$PEAR\\|pear\$/"
(buffer-file-name))
      (string-match "\.php$"
(buffer-file-name))))))

Here are vim rules for the same
thing:
set expandtab
set shiftwidth=4
set softtabstop=4
set tabstop=4

At 14:23 21.07.2006, you wrote:
On

http://code.campware.org/projects/campsite/wiki/CodingStandards
there is written:
1. Use a tab of four (4) characters, and set your editor to insert
spaces
instead of tabs.
But it seems all php script use tab instead of spaces. What should I
use?
Sebastian

Micz Flor - micz@mi.cz

content and media
development
http://mi.cz
--------------------------------------------------------

http://www.campware.org
--
http://www.suemi.de

http://www.redaktionundalltag.de
--------------------------------------------------------

Howdy, Stranger!

Categories

Poll

Top Posters