phpwcms Support Forum

Hi,


why does the setup.php with a new installation complains about the missing tmp folder and the two subfolders thumb_list and thumb_preview, when Oliver Georgi said that they are not necessary anymore?

Can I then ignore the error messages?


Joachim

jscholtysik wrote:Hi,


why does the setup.php with a new installation complains about the missing tmp folder and the two subfolders thumb_list and thumb_preview, when Oliver Georgi said that they are not necessary anymore?

Can I then ignore the error messages?


Joachim

thats the way I read OGs note

marco wrote:

Oliver Georgi wrote:as described: setup process has to be enhanced/changed. will do that a bit in next release.

The "old" temp folder is not neccessary anymore (should be) - maybe there are some not changed content part settings like bid.

marco wrote:"error:> proof recipient - email format error;

you have to fill in a recipient before sending content part.

Oliver

I am not yet sending anything; I was only trying to define the content part first to include the mail form on a page; that's when I got the error; no big deal for me, I am just testing and I only wanted to bring this to your attention in case it is something that needs fixing.

hello marco

did you add an reciient in the content part "email from" before you safe your content part!? that was what OG means! with sending content part!

jscholtysik wrote:Hi,


why does the setup.php with a new installation complains about the missing tmp folder and the two subfolders thumb_list and thumb_preview, when Oliver Georgi said that they are not necessary anymore?

Can I then ignore the error messages?


Joachim

hello joachim

never forget that this is not the final release! so there can be differences while the setup of an new installation! so ignore this error i would say!

Pappnase wrote:[
hello marco

did you add an reciient in the content part "email from" before you safe your content part!? that was what OG means! with sending content part!

No, I did not, I must have missed the field.

marco wrote:

Pappnase wrote:[
hello marco

did you add an recipient in the content part "email from" before you safe your content part!? that was what OG means! with sending content part!

No, I did not, I must have missed the field.

hello

so did you test it with an e-mail adress in the recipient field!?

has anyone tried the content-anywhere thingy?
[edit]: already found out - u just put {CONTENT} in the main block and {LEFT} in the left and so on. cool.

BTW, Oli : Respekt...

Pappnase wrote:

marco wrote:

Pappnase wrote:[
hello marco

did you add an recipient in the content part "email from" before you safe your content part!? that was what OG means! with sending content part!

No, I did not, I must have missed the field.

hello

so did you test it with an e-mail adress in the recipient field!?

Yes, that was indeed the problem, no error this time.

Just a thought, would it make sense for the mandatory fields in the content parts to have some sort of indicator at some point; maybe a red asterisk or something?

webwesen wrote:has anyone tried the content-anywhere thingy?
[edit]: already found out - u just put {CONTENT} in the main block and {LEFT} in the left and so on. cool.

BTW, Oli : Respekt...

yes i have tested ist and it runs!

Hi, great release Oliver, really

I have a problem with the page refresh after some changes.
When I delete a content part from an article, or just hiding it, Im not able to see the changes until I don't edit the article too.
I can just update the article without changes in order to see the effects in the frontend page.
Otherwise, I'm not able to see such changes.

Hi sustia,

i got the same effect.

changing something in an articleand save the changes and look in frontend don't see the changes.

Go back to an article, change something, save again and see THAN in frontend the changes.

There is a step not working correct i guess...

That's caching

Workaround: set cache timeout in conf.inc.php = 0;

Maybe something is not updated well on your install or there is really a bug. If possible make a screenshot of editing. maybe I can see what and why this is not working for you. Normally every change/add resets cache timeout.

Oliver

fine - thank you oliver :-)

Oliver Georgi wrote:That's caching - set cache timeout in conf.inc.php = 0;

Oliver

how much does the cache speed up the load of pages?

around 50x based on complexity of page/article. And not only speed up - server load is much lower.

Oliver