phpWCMS Version 1.2.3 - founded Changes and new Stuff

[Pappnase]

Are you a moderator...

If there was more talk on the forum to better structure the way info was presented, faq, etc etc, then many of the problems would not arrise from all the users, as there would be a knowledge base...

if you have an idea then I suppose we could look into it...
the dev forum was developed so that there was a central place for all the dev stuff that OG does not get involved in...

I am sure that if some users where to help out like Pappnase has with his docu site then we could make this forum more user friendly, however this is a problem when you are not a moderator, as you dont have any rights... !!!

oh well what can you do when you are trying to help out.....

hello

but as you know OG was never happy about the second forum! and so i thinke here isthe forum to alk all about the new stuff not the dev forum! your dev forum / site is for hacks an enhancements.
also i set this topic to important and this thread was only open to publish what changes would be found in the new release! so why don't you post constructive threads.

the second forum was the reason why i split up the work with brans. i told him a seocnd forum ok but NON-PUBLIC only for the developers that they can talk together. and an phpwcms to show and comment the hacks and enhancements.

so we have now the moement waht OG and also me never want.

[Kosse]

My contribution is OT but... I think you are right Pappnase, this is THE forum, the other one is just to publish (not to discuss) and organise a little bit the hacks and enhancements (difficult to find everything classified in here ) , brans does it ok and it's a usefull ressource. It could even be a site or a blog, but it looks like a forum, who cares in fact? OK, I'll stop saying things because this post is supposed to talk about the new features and tags of 1.2.3

Cheers

[Ben]

Am I missing something with the SPAW / Filemanager integration? I've installed 1.2.3 DEV twice already, and SPAW's insert image popup works the same now as it has for quite some time - It simply shows the cryptic urls of the images in the in the "phpwcms" folder. This is nothing new.

[jscholtysik]

Hi all,


it seems that there is a new replacement tag called {TIMER}, located in the index.php of the cms root folder. It should show the processing time of an article, but when I delete all comment signs for this timer function and try this RT, nothing will be replaced in my test content part...


Joachim

[Kosse]

Works with me...
You have to uncomment at the top of index.php

Code: Select all

// this is for testing only
// returns how long this script is processed
// remove comments // to use this - look at the end of this
// page too
//
require ("include/inc_ext/phpsniff/phpTimer.class.php");
$timer =& new phpTimer();
$timer->start('main');

and the bottom too.

Btw, this already existed in 1.2.1

[jscholtysik]

Hi Kosse,


tried it once more, but didn't get it!


What did you insert into your content or content part?


Joachim

[Kosse]

Oops, my bad didn't try the {timer}, just uncommented the lines and the timer appears on page, but not as a RT (it looks like it though), maybe someone?

[pico]

but it's not new - was in 1.1RCx also

[jsw_nz]

"* SPAW Editor (only IE) works with Imagebrowser and shows Images wich are uploaded with phpWCMS-Filemanager"

Tried it using Pappnase's test installation....
and like Ben said..no difference....
Spaw also seems to be plagued by other issues.

Spaw image browser throws occassional javascript errors
Selected images do not scale to proper size
does not even create the proper relative path (add reduntant directory)
by default the image upload option is disabled...

obviously some of these can be fixed by proper config settings
but to be honest, Spaw is a wee bit frustrating (in dev releases so far)

maybe not finished yet.....

[Mobius]

What is with the DHTML menues?
Is it working in this release?

[Morgen]

Hi!

conf.php:
$phpwcms["wysiwyg_editor"] = 2; //0 = no wysiwyg editor, 1 = HTMLarea, 2 = FCKeditor, 3 = browser based

Im use FCKeditor. Editing Article.. press save&close button
and not saving the modified article

[jsw_nz]

Might be the proverbial cache timeout issue:
might want to change config file to:

$phpwcms["cache_timeout"] = 0;

Although I thought this issue was resolved....earlier

[jsw_nz]

Also wanted to ask if anyone has gotten the FORUM content part working?
wounld be far better than guestbook feature I am using occasionally....

[jsw_nz]

Not sure about this, since it has yet to be reported. On my local installation of 123, I am finding that wcms does not render the page margin info from admin | page layout:

Code: Select all

topmargin="0" leftmargin="0" marginwidth="0" marginheight="0"

This has been standard from 'day one' of wcms.....
Is there something I am overlooking......

Actual data for layout is stored as a medium blob in phpwcms_pagelayout , so hard to decipher, guessing that the insert statement is not passing the margin data from admin: page layout interface.

UPDATE:
Was able to fix this by swapping the 123 code for 122 code:

Code: Select all

function get_body_attributes($values)

inside:

include/inc_front/front.func.inc.php

certanly not an ideal situation, but now the body attributes are being returned.
Have others experienced this issue?

[jsw_nz]

Getting error on page with wysiwyg FckEditor 2 in newletter section. (DEV 123) Wanted to ask if others can confirm. Trying to get absolute urls inside newletter to work. I do have a unique situation, where I am using subdirectory inside localhost and have edited both

connector.php

Code: Select all

$GLOBALS["UserFilesPath"] = '/phpwcms_dev_123/picture/' ;

line 26 and line 36

and

frmresourceslist.html

Code: Select all

<a href="#" onclick="OpenFile(\'http://localhost' + fileUrl + '\');return false;">

line 64

So far 123 newsletter function is not working...

When I click on image button (FCK) window does not spawn.
error on page

This could be settings of localhost that are confounding FCK, not sure.

Also discovered an issue inside 122 and other dev releases, when loading FCK editor inside newsletter section....

Apparently certain related files need to be downloaded (and be in cache) in advance. I had to use standard article edit to download full FCK interface in advance)... otherwise the FCK editor interface does not load inside newsletter module.

Spent a considerable amount of time on these issues.....
very frustrating atm.

I do realise these issues are outside the scope of wcms, but for installations that need to support newsletter creation via wysiwyg editors, none of the given apps are user friendly. Spaw strips out absolute URLS (dev releases), 123 Fck throws page error, HTML area is not very useful, since it requires user to provide/paste full address to image file.