Re: [campsite-support] Transfer Smarty Variable To php - Newscoop Support Discussions on Sourcefabric Forum

import

You can use the smarty custom function assign:

{{ assign var=gender value=`$campsite->user->gender` }}
{{ if $gender == "M" }}Male{{ /if }}
{{ if $gender == "F" }}Female{{ /if }}

Mugur

On Thu, Apr 16, 2009 at 6:18 PM, wrote:

> Author: Lee
> Link: http://code.campware.org/phorum/read.php?8,7022,7022#msg-7022
>
> --------------------------------------------------------------------------------
>
> I hope this isn't a stupid question.
>
> I am trying to evaluate a smarty variable within php, and no matter what I
> try I am unsuccessful. Can anyone shed some light on how that is done (or if
> it can be done)?
>
> What I am trying to do is take the campsite user variable "gender" and have
> the output display as "Male" or "Female" instead of "M" or "F". Once a user
> has registered, their gender will not change (OK, there are a few weird
> exceptions out there but I'm not going there). Accordingly, when I display a
> registered user's profile, I merebly want to show Male or Female.
>
> Hope that made sense. I tend to ramble!
>
> --
> Sent from Campware Forums
> http://code.campware.org/phorum
>

import

Hi,

I just realised that the Campsite Manual v3.1 doesn't have anything
about the new upgrade that is written anyhow in the campsite folder
you get from Sourceforge.

It actually says that

Drop the 3.2 sources over the existing 3.0/3.1 install, open a browser
and make a request for the publication home page: http://[site_name]
The upgrade will be performed automatically when you make the first
request to the publication site or to the Campsite admin interface.

But what is missing that which files shouldn't be overwritten?
Obviously configuration files should be left intact.
What else? Template files as well I have in the backup copy, so I need
to put them back.

Gene

import

Replying to my own mail:
I continued inputting all possible Campsite files in the server and
then went to the site to upgrade.

I got a message that it is upgrading and then immediately again:
Error: while upgrading the database: Can't create the index.php file.

I removed index.php and tried again. It happened the same thing.
Something to do with permissions?
Tell me what else we need to know to solve the issue. The previous
version is 3.1.2.

Gene

On 23.4.2009, at 9.57, Generare Management Department wrote:

> Hi,
>
> I just realised that the Campsite Manual v3.1 doesn't have anything
> about the new upgrade that is written anyhow in the campsite folder
> you get from Sourceforge.
>
> It actually says that
>
> Drop the 3.2 sources over the existing 3.0/3.1 install, open a browser
> and make a request for the publication home page: http://[site_name]
> The upgrade will be performed automatically when you make the first
> request to the publication site or to the Campsite admin interface.
>
> But what is missing that which files shouldn't be overwritten?
> Obviously configuration files should be left intact.
> What else? Template files as well I have in the backup copy, so I
> need to put them back.
>
> Gene
>

import

Hi again!

I could not find any thread about the upgrade issues. Do we have one
in the forum?
It is really unpleasent to have a blank site for 1 day already. Any
debugging tool for these issues?

/G

On 23.4.2009, at 11.21, Generare Management Department wrote:

> Replying to my own mail:
> I continued inputting all possible Campsite files in the server and
> then went to the site to upgrade.
>
> I got a message that it is upgrading and then immediately again:
> Error: while upgrading the database: Can't create the index.php file.
>
> I removed index.php and tried again. It happened the same thing.
> Something to do with permissions?
> Tell me what else we need to know to solve the issue. The previous
> version is 3.1.2.
>
> Gene
>
> On 23.4.2009, at 9.57, Generare Management Department wrote:
>
>> Hi,
>>
>> I just realised that the Campsite Manual v3.1 doesn't have anything
>> about the new upgrade that is written anyhow in the campsite folder
>> you get from Sourceforge.
>>
>> It actually says that
>>
>> Drop the 3.2 sources over the existing 3.0/3.1 install, open a
>> browser
>> and make a request for the publication home page: http://[site_name]
>> The upgrade will be performed automatically when you make the first
>> request to the publication site or to the Campsite admin interface.
>>
>> But what is missing that which files shouldn't be overwritten?
>> Obviously configuration files should be left intact.
>> What else? Template files as well I have in the backup copy, so I
>> need to put them back.
>>
>> Gene
>>
>
>

import

After dropping the 3.2 sources over the old ones change the file ownership
to the apache user. E.g.:
chown -R www-data:www-data [campsite_dir]

Mugur

On Thu, Apr 23, 2009 at 11:21 AM, Generare Management Department <
management@generare.com> wrote:

> Replying to my own mail:I continued inputting all possible Campsite files
> in the server and then went to the site to upgrade.
>
> I got a message that it is upgrading and then immediately again:
> Error: while upgrading the database: Can't create the index.php file.
>
> I removed index.php and tried again. It happened the same thing. Something
> to do with permissions?
> Tell me what else we need to know to solve the issue. The previous version
> is 3.1.2.
>
> Gene
>
> On 23.4.2009, at 9.57, Generare Management Department wrote:
>
> Hi,
> I just realised that the Campsite Manual v3.1 doesn't have anything about
> the new upgrade that is written anyhow in the campsite folder you get from
> Sourceforge.
>
> It actually says that
>
> *Drop the 3.2 sources over the existing 3.0/3.1 install, open a browser*
> *and make a request for the publication home page: http://[site_name]*
> *The upgrade will be performed automatically when you make the first*
> *request to the publication site or to the Campsite admin interface.*
>
> But what is missing that which files shouldn't be overwritten? Obviously
> configuration files should be left intact.
> What else? Template files as well I have in the backup copy, so I need to
> put them back.
>
> Gene
>
>
>
>
>

import

Hi again!

Longing for getting the great news engine back visible...

Not sure if my automatic error report went through from the site admin
because it comes to the same error form again after the report. Thus I
write it here.

So, I'm still trying to upgrade without a solution. I realised that
web root itself had not enough permissions and I set that higher and
then the upgrade process doesn't give any errors anymore on the public
side of the engine but the result is a blank page.

Then I looked the admin side and I get this error:
camp_report_bug() called at [/home/webadmin/customer/html/classes/
CampPlugin.php:168]
CampPlugin::GetPluginInfos() called at [/home/webadmin/customer/html/
classes/CampPlugin.php:210]
CampPlugin::ExtendNoMenuScripts() called at [/home/webadmin/customer/
html/admin.php:51]

For example the file admin.php doesn't have 51 lines in it. Is that
number referring to the lines?

Gene

On 24.4.2009, at 9.40, Mugur Rus wrote:

> After dropping the 3.2 sources over the old ones change the file
> ownership to the apache user. E.g.:
> chown -R www-data:www-data [campsite_dir]
>
> Mugur
>
> On Thu, Apr 23, 2009 at 11:21 AM, Generare Management Department > > wrote:
> Replying to my own mail:
> I continued inputting all possible Campsite files in the server and
> then went to the site to upgrade.
>
> I got a message that it is upgrading and then immediately again:
> Error: while upgrading the database: Can't create the index.php file.
>
> I removed index.php and tried again. It happened the same thing.
> Something to do with permissions?
> Tell me what else we need to know to solve the issue. The previous
> version is 3.1.2.
>
> Gene
>
> On 23.4.2009, at 9.57, Generare Management Department wrote:
>
>> Hi,
>>
>> I just realised that the Campsite Manual v3.1 doesn't have anything
>> about the new upgrade that is written anyhow in the campsite folder
>> you get from Sourceforge.
>>
>> It actually says that
>>
>> Drop the 3.2 sources over the existing 3.0/3.1 install, open a
>> browser
>> and make a request for the publication home page: http://[site_name]
>> The upgrade will be performed automatically when you make the first
>> request to the publication site or to the Campsite admin interface.
>>
>> But what is missing that which files shouldn't be overwritten?
>> Obviously configuration files should be left intact.
>> What else? Template files as well I have in the backup copy, so I
>> need to put them back.
>>
>> Gene
>>
>
>

import

Sorry again, but the error in admin side also had this title that I
forgot to put here:
"Error Message: Use of undefined constant CS_PATH_PLUGINS - assumed
'CS_PATH_PLUGINS' "

/G

On 26.4.2009, at 13.30, Generare Management Department wrote:

> Hi again!
>
> Longing for getting the great news engine back visible...
>
> Not sure if my automatic error report went through from the site
> admin because it comes to the same error form again after the
> report. Thus I write it here.
>
> So, I'm still trying to upgrade without a solution. I realised that
> web root itself had not enough permissions and I set that higher and
> then the upgrade process doesn't give any errors anymore on the
> public side of the engine but the result is a blank page.
>
> Then I looked the admin side and I get this error:
> camp_report_bug() called at [/home/webadmin/customer/html/classes/
> CampPlugin.php:168]
> CampPlugin::GetPluginInfos() called at [/home/webadmin/customer/html/
> classes/CampPlugin.php:210]
> CampPlugin::ExtendNoMenuScripts() called at [/home/webadmin/customer/
> html/admin.php:51]
>
> For example the file admin.php doesn't have 51 lines in it. Is that
> number referring to the lines?
>
> Gene
>
> On 24.4.2009, at 9.40, Mugur Rus wrote:
>
>> After dropping the 3.2 sources over the old ones change the file
>> ownership to the apache user. E.g.:
>> chown -R www-data:www-data [campsite_dir]
>>
>> Mugur
>>
>> On Thu, Apr 23, 2009 at 11:21 AM, Generare Management Department >> > wrote:
>> Replying to my own mail:
>> I continued inputting all possible Campsite files in the server and
>> then went to the site to upgrade.
>>
>> I got a message that it is upgrading and then immediately again:
>> Error: while upgrading the database: Can't create the index.php file.
>>
>> I removed index.php and tried again. It happened the same thing.
>> Something to do with permissions?
>> Tell me what else we need to know to solve the issue. The previous
>> version is 3.1.2.
>>
>> Gene
>>
>> On 23.4.2009, at 9.57, Generare Management Department wrote:
>>
>>> Hi,
>>>
>>> I just realised that the Campsite Manual v3.1 doesn't have
>>> anything about the new upgrade that is written anyhow in the
>>> campsite folder you get from Sourceforge.
>>>
>>> It actually says that
>>>
>>> Drop the 3.2 sources over the existing 3.0/3.1 install, open a
>>> browser
>>> and make a request for the publication home page: http://[site_name]
>>> The upgrade will be performed automatically when you make the first
>>> request to the publication site or to the Campsite admin interface.
>>>
>>> But what is missing that which files shouldn't be overwritten?
>>> Obviously configuration files should be left intact.
>>> What else? Template files as well I have in the backup copy, so I
>>> need to put them back.
>>>
>>> Gene
>>>
>>
>>

import

Hi again!

I just need to report what looks like solved the issue although it is
yet not showing the articles and need to see the encoding fix as well.

Anyhow, uploading the upgrade on the server, folder "templates" in the
new installation package didn't have any templates at all and it
replaced the folder in the server partially. So, not all were deleted
but part of them were and for example index.tpl was missing. I
replaced that and the others and now the public side front page is
visible. Also admin login looks fine, let's c how it is inside... Wink

Just thought to report that others can watch out...

Gene

On 26.4.2009, at 15.40, Generare Management Department wrote:

> Sorry again, but the error in admin side also had this title that I
> forgot to put here:
> "Error Message: Use of undefined constant CS_PATH_PLUGINS -
> assumed 'CS_PATH_PLUGINS' "
>
> /G
>
> On 26.4.2009, at 13.30, Generare Management Department wrote:
>
>> Hi again!
>>
>> Longing for getting the great news engine back visible...
>>
>> Not sure if my automatic error report went through from the site
>> admin because it comes to the same error form again after the
>> report. Thus I write it here.
>>
>> So, I'm still trying to upgrade without a solution. I realised that
>> web root itself had not enough permissions and I set that higher
>> and then the upgrade process doesn't give any errors anymore on the
>> public side of the engine but the result is a blank page.
>>
>> Then I looked the admin side and I get this error:
>> camp_report_bug() called at [/home/webadmin/customer/html/classes/
>> CampPlugin.php:168]
>> CampPlugin::GetPluginInfos() called at [/home/webadmin/customer/
>> html/classes/CampPlugin.php:210]
>> CampPlugin::ExtendNoMenuScripts() called at [/home/webadmin/
>> customer/html/admin.php:51]
>>
>> For example the file admin.php doesn't have 51 lines in it. Is that
>> number referring to the lines?
>>
>> Gene
>>
>> On 24.4.2009, at 9.40, Mugur Rus wrote:
>>
>>> After dropping the 3.2 sources over the old ones change the file
>>> ownership to the apache user. E.g.:
>>> chown -R www-data:www-data [campsite_dir]
>>>
>>> Mugur
>>>
>>> On Thu, Apr 23, 2009 at 11:21 AM, Generare Management Department >>> > wrote:
>>> Replying to my own mail:
>>> I continued inputting all possible Campsite files in the server
>>> and then went to the site to upgrade.
>>>
>>> I got a message that it is upgrading and then immediately again:
>>> Error: while upgrading the database: Can't create the index.php
>>> file.
>>>
>>> I removed index.php and tried again. It happened the same thing.
>>> Something to do with permissions?
>>> Tell me what else we need to know to solve the issue. The previous
>>> version is 3.1.2.
>>>
>>> Gene
>>>
>>> On 23.4.2009, at 9.57, Generare Management Department wrote:
>>>
>>>> Hi,
>>>>
>>>> I just realised that the Campsite Manual v3.1 doesn't have
>>>> anything about the new upgrade that is written anyhow in the
>>>> campsite folder you get from Sourceforge.
>>>>
>>>> It actually says that
>>>>
>>>> Drop the 3.2 sources over the existing 3.0/3.1 install, open a
>>>> browser
>>>> and make a request for the publication home page: http://
>>>> [site_name]
>>>> The upgrade will be performed automatically when you make the first
>>>> request to the publication site or to the Campsite admin interface.
>>>>
>>>> But what is missing that which files shouldn't be overwritten?
>>>> Obviously configuration files should be left intact.
>>>> What else? Template files as well I have in the backup copy, so I
>>>> need to put them back.
>>>>
>>>> Gene
>>>>
>>>
>>>

import

Did you upgrade to 3.2.1? I tested it and couldn't reproduce your problem.
Please try to clean the campsite directory and do a clean install. Do a site
backup first and restore it after the campsite install.

Mugur

On Sun, Apr 26, 2009 at 1:30 PM, Generare Management Department <
management@generare.com> wrote:

> Hi again!
> Longing for getting the great news engine back visible...
>
> Not sure if my automatic error report went through from the site admin
> because it comes to the same error form again after the report. Thus I write
> it here.
> So, I'm still trying to upgrade without a solution. I realised that web
> root itself had not enough permissions and I set that higher and then the
> upgrade process doesn't give any errors anymore on the public side of the
> engine but the result is a blank page.
>
> Then I looked the admin side and I get this error:
> camp_report_bug() called at
> [/home/webadmin/customer/html/classes/CampPlugin.php:168]
> CampPlugin::GetPluginInfos() called at
> [/home/webadmin/customer/html/classes/CampPlugin.php:210]
> CampPlugin::ExtendNoMenuScripts() called at
> [/home/webadmin/customer/html/admin.php:51]
>
> For example the file admin.php doesn't have 51 lines in it. Is that number
> referring to the lines?
>
> Gene
>
> On 24.4.2009, at 9.40, Mugur Rus wrote:
>
> After dropping the 3.2 sources over the old ones change the file ownership
> to the apache user. E.g.:
> chown -R www-data:www-data [campsite_dir]
>
> Mugur
>
> On Thu, Apr 23, 2009 at 11:21 AM, Generare Management Department <
> management@generare.com> wrote:
>
>> Replying to my own mail:I continued inputting all possible Campsite files
>> in the server and then went to the site to upgrade.
>>
>> I got a message that it is upgrading and then immediately again:
>> Error: while upgrading the database: Can't create the index.php file.
>>
>> I removed index.php and tried again. It happened the same thing. Something
>> to do with permissions?
>> Tell me what else we need to know to solve the issue. The previous version
>> is 3.1.2.
>>
>> Gene
>>
>> On 23.4.2009, at 9.57, Generare Management Department wrote:
>>
>> Hi,
>> I just realised that the Campsite Manual v3.1 doesn't have anything about
>> the new upgrade that is written anyhow in the campsite folder you get from
>> Sourceforge.
>>
>> It actually says that
>>
>> *Drop the 3.2 sources over the existing 3.0/3.1 install, open a browser*
>> *and make a request for the publication home page: http://[site_name]*
>> *The upgrade will be performed automatically when you make the first*
>> *request to the publication site or to the Campsite admin interface.*
>>
>> But what is missing that which files shouldn't be overwritten? Obviously
>> configuration files should be left intact.
>> What else? Template files as well I have in the backup copy, so I need to
>> put them back.
>>
>> Gene
>>
>>
>>
>
>

Howdy, Stranger!

Categories

Poll

Top Posters