pre1.2.9 nightly-build

[flip-flop]

Hi Yves,

at this moment it isn´t assign to a specified use. (I can´t find it in any file out side from /setup/ and /config/).
Changelog 1.2.8:

[ADD] New settings for MySQL charset and collation. In "conf.inc.php" manually add $phpwcms['db_charset'] and $phpwcms['db_collation'] at the moment. This will be integrated into the setup process (completely rewritten).
[ADD] Some additional information for setup script (MySQL Client version and GD information).

Regards Knut

[DeXXus]

Questions:
Do I really need the "db_collation'" option ?
Do I really need the "db_version" option ?

It ~looks~ like they are BOTH implemented.
db_version is implemented and calls up whichever .SQL file (phpwcms_init_410.sql -or- phpwcms_init_323.sql) matches the version in"setup.check.inc.php":

Code: Select all

$sql_data = 'default_sql/'.(($phpwcms['db_version'] > 40100) ? 'phpwcms_init_410.sql' : 'phpwcms_init_323.sql');
$sql_data = read_textfile($sql_data);

AND
db_collation is implemented and sends queries with appropriate charset -in- "dbcon.inc.php":

Code: Select all

	// set DB to compatible mode
	@mysql_query("SET SQL_MODE='MYSQL323'", $db);

	// Send charset used in phpwcms for every query
	if(!empty($phpwcms['db_charset'])) {
		$sql = "SET NAMES '".$phpwcms['db_charset']."'";
		if(!empty($phpwcms['db_collation'])) {
			$sql .= " COLLATION '".$phpwcms['db_collation']."'";
		}
		mysql_query($sql, $db);
	}

}

[StudioZ]

Thank you guys: Knut and DeXXus for your insights on "db_collation" and "db_version".

Another issue:
I was testing with the new "database: save form results" option in the "email contact form" and... for a reason I don't understand, the accentued characters submitted in the form like éèà etc.. are being lost and thus.. not written in the database and of course not spitted out in the .xls file results.

Could it be just the way my conf file is set...?

Cheers,

Yves

[StudioZ]

SOLVED
I discovered that this is only happening on my Mac.
No problems on my PC. Will now open and use this new
usefull feature (.xls) only on my Win Machine.
No problems.

Notes:
01. In the .xls file results, only the #Date column stays empty
02. If I use an hidden field for {DATE_MEDIUM} the date is outputted as 2007.01.28 where in my conf.template_default.inc.php file I have:
$template_default['date']['medium'] = 'Y.m.d H:i';

Cheers,

Yves

[StudioZ]

Notes:
01. In the .xls file results, only the #Date column stays empty
02. If I use an hidden field for {DATE_MEDIUM} the date is outputted as 2007.01.28 where in my conf.template_default.inc.php file I have:
$template_default['date']['medium'] = 'Y.m.d H:i';

SOLVED

01.
I found that this date issue ONLY happens in my test site where I upgraded from 1.2.8 to pre1.2.9

Solution: Fix the structure:
table: phpwcms_formresult
Field: formresult_createdate
add in default column: CURRENT_TIMESTAMP (click the checkbox)
and remove the NULL value

02.
Found out that this field can be formatted the way you want it, from inside Excel.


Cheers,

Yves

[flip-flop]

NAV_LIST_UL in V1.2.9pre

Hi at all,

two hints using the NAV_LIST_UL:

1. The link tracing don´t work in V1.2.9pre 20062011.
The .active class (if you use it) is lost in the parent link.
Solution:
/include/inc_front/front.func.inc.php:
Exchange line 3239:

Code: Select all

if($active_class != '' && $key == $GLOBALS['aktion'][0]) { 

to:

Code: Select all

if($active_class != '' && isset($GLOBALS['LEVEL_KEY'][$key])) {

2. A new parameter is available in wrap_ul_div:
@string $parameter =
"menu_type, start_id, max_level_depth, class_path, class_active, ul_id_name, wrap_ul_div(0 = off, 1 = <div>, 2 = <div id="">, 3 = <div class="navLevel-0">), wrap_link_text(<em>|</em>)"

E.g.: {NAV_LIST_UL:F,0,4,,active,,3}
For every level there is an output like

Code: Select all

<div class="navLevel-0">
<ul>
  <li class="sub_no">.....
  <li class="sub_ul active">.......
    <div class="navLevel-1">.....
    <ul>
      <li class="sub_no active">......
    </ul>
    </div>
  </li>
 <li class="sub_no">...
</ul>
</div>

It is an excellently parameter. This makes the CSS simple easy.
Basics: http://www.phpwcms.de/forum/viewtopic.php?t=12165
CSS basics: http://www.phpwcms.de/forum/viewtopic.php?t=12716

-------------------
3. Error using GT mode with UTF-8 charset: "Warning: cannot yet handle MBCS in html_entity_decode()!"
http://www.phpwcms.de/forum/viewtopic.php?p=68589#68589


Regards Knut

[StudioZ]

ouuuppsss
Just discovered a path issue with the Newsletter validating process for:
http://www.malouin.ws/design/index.php?fr_liste

In my conf.inc.php file, the 1.2.9 setup has automagicaly putted in there:
$phpwcms['site'] = 'http://www.malouin.ws/';
$phpwcms['DOC_ROOT'] = $_SERVER['DOCUMENT_ROOT']; // real DOC_ROOT seems to be: '/home/malouin/public_html//inc'
$phpwcms['root'] = 'design'; // default: ''
No problem so far...

The problem is when you register and click on the link you received in the email asking you to validate:
Template tag used: {NEWSLETTER_VERIFY}
Outputs in the email as:
http://www.malouin.ws/design/verify.php ... ashHereEtc.=

When the user clicks on the email link, the link then changes to:
http://www.malouin.ws/home/malouin/public_html/design/include/inc_act/act_newsletter.php?i=VjpabHFyYLongHashHereEtc.=

Of course this link generates a 404 error page:
Not Found
The requested URL /home/malouin/public_html/design/include/inc_act/act_newsletter.php was not found on this server.

Does anyone sees something that I might overlooked here ?


Thanks,

Yves

[StudioZ]

"Heh-heh-heh . . .
Have you heard the news?
(News? What news?) ..."
-- F.Z.

Check: http://www.phpwcms.de/forum/viewtopic.php?t=13742

Cheers,

Yves

[jsw_nz]

OliG says

I have a master plan in my mind

got to believe that it will be worth the wait ....

thanks yves

[StudioZ]

got to believe that it will be worth the wait ....
thanks yves

Most Welcome JSW_NZ
You know...
Something that stroke my mind in Oliver's post has been this:

... There is a German saying: “Zuviele Köche verderben den Brei” (Too many cooks spoil the broth.).

This is exactly what I beleive explains why Mambo was (if I well recall) so graphically unpredictable and... why PhpWCMS is so tight and versatile
Yep. All the PhpWCMS delays have always worth the wait

Cheers,

Yves
True PhpWCMS Evangelist

[sustia]

Great news!!

I'll wait with patience the week end, and I'm absolutely sure that worth the wait

[Quizmaster]

Amen !!!

[jsw_nz]

Just wanted to post this -
I am guessing the entire community is looking
for any updates on the new version.

And am guessing the new version will be stellar

For the sake of opening up comminication -
I wanted to ask OLIG (the CMS Beethoven) if there might be might provision for a weekly/bi-weekly update on progress towards 1.30 (2.0) -


this is both in the spirit of the community expectations' as well as acknowledging the community's complete willingness - to be patient

to await SUPERIOR solution.

So OLIG - if you read this - just wanted to ask for a brief weekly (or) every other weekly report - in a few sentences.....
might be possible.

all the best

[Quizmaster]

Just wanted to post this -
I am guessing the entire community is looking
for any updates on the new version.

And am guessing the new version will be stellar

For the sake of opening up comminication -
I wanted to ask OLIG (the CMS Beethoven) if there might be might provision for a weekly/bi-weekly update on progress towards 1.30 (2.0) -


this is both in the spirit of the community expectations' as well as acknowledging the community's complete willingness - to be patient

to await SUPERIOR solution.

So OLIG - if you read this - just wanted to ask for a brief weekly (or) every other weekly report - in a few sentences.....
might be possible.

all the best

And again .... AMEN !!!

[cyber-james]

And again .... AMEN !!!

Why that? Listen up! Its a new one there!

cy

Thank you Oliver!