New Module - Section Picker (aka Global Blocks)

[Ruud]

Section Picker does not work when accessing a section of the module Randombanner
WB 2.8.2 R1466

Does it work when using a stable WB release (2.8.1)?

It makes not much sense to "complain" about the functioning of any modules when a non-stable core is used.

[Hans Toolbox]

Version 2.8.1 / Revision 1287
SM2 from r1464

Unfortunately, the same problem

[snark]

Met een nieuwsmodule waarbij je alleen t korte tekst eld gebruikt om een afbeelding + link te plaatsen en dan via een anynews op random order ben je veel flexibeler en beter af.

Aan klanten is t ook makkelijker uitleggen omdat ze dan een eenvormiger websitebeheer hebben (uitgaand van dat ze een nieuwspagina in hun website hebben)

Makkelijker en beter werkend kan gewoon niet, als je dan in de ck editor ook nog een opmaaksjabloontje maakt of de img style van de div definieert zijn de banners ook nog allemaal even groot

[Ruud]

is an error: Undefined variable: gname

The problem is the Modul "Randombanner" ?

Well at least the gname is used somewhere in the randombanner module. So that will be the problem.

1. Does it work without the sectionpicker?

2. You never explained what is was that didn't work.

3. Do you have any detailed errormessage?

BTW: For me it will not display anything because my add-filter will -by default- remove any image that holds the word banner somewhere in the image url.

[Hans Toolbox]

1. Does it work without the sectionpicker?
Yes, random banner module works

2. You never explained what is was that didn't work.
with section picker: without random pictures, it shows all the images together

3. Do you have any detailed errormessage?
No further message

[Ruud]

In that case, the answer was already in this thread before.

WB cannot include the frontend.css from another module than the module that was used (section picker)
Add any info from the Randombanner frontend.css into your template css. That will probably do the trick.

[Hans Toolbox]

It was the right suggestion
frontend.css was embedded
but randombanner.js (frontend.js) was not loaded
Thank you - It works  

[Roych]

One question

Im usin section picker for some of my pages and it works well, but doesent show me text like čšž where can I change the charset for sectionpicker module. Is this possible? I have looked in all files included in the module but couldnt find the way.


Thank you

R.

[Ruud]

You cannot because the section_picker does not display content. It just loads the module/view.php of another section.

If you are viewing th sections directly, do they show correct?

Does it happen with all kind of pages/sections?

Are you using the correct encoding setting (in the /admin/settings page)

Can we have a look?

[Roych]

Hi

Thx for help

If I show the page directli it shows correct but with section picker it doesent.
I have the all the right setings in admin.

here is the test page: http://www.as-press.si/aspress_2011

the buttons Domov and Domov 2.

Domov is created with Section picker (look at the read more buton "Preberi več") the Č is not right. even the form underneath is not right.

But Domov 2 is created directly and everything works fine.


Thx

[Roych]

I have noticed that this only happens with Google Chrome!

Any idea?

[Ruud]

I have noticed that this only happens with Google Chrome!

I noticed the same thing.

There are some strange things in your template (like: <meta charset="UTF-8">)
Fot the rest I would suggest to first fix all errors in the template. Some of the errors could really break a brower functionality.

[Roych]

I know a stupid question, but how do I repair those errors in which file?

On my FTP or how. Where do I find those files?

I have never done that before

Please help would really like to correct this. I have tryed to look for a tutorial but nothing really helpfull.

thank you.

[Ruud]

Have a look at thehelp pages on this website: http://www.websitebaker2.org/en/help/designer-guide/creating-a-wb-template.php
It will explain how WB templates are built.

The errors are all listed in the validator (link in my orevious post).
The validator tries to explain what is wrong with the site.
For the rest it is html/css knowledge. The help pages will have some links to helpfull websites about that too.

[Roych]

Thx

I tried to go through help but nothig helpfull came up. 

I know some css and HTML and do know how the templates are built but still don't know where to find those files.

So let's say i have an error here:

Line 9, Column 289: end tag for "link" omitted, but OMITTAG NO was specified
…s_2011/modules/jqueryadmin/plugins/Superfish/css/superfish.css" media="screen">

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Where do I have to go to change this. I have acces to all the files. I would know how to repair it if I would know where to find those files.
Line 9, Column 289 where?

"index.php" or in my templates folder or....

I have looked everywhere? 




"I know, a nother one of those....."

thank you!

R.

[Ruud]

your template is in /aspress_2011/template/AS-NOVA/index.php
In the same directory (and subdirectories) you will find the css and a lot of javascript stuff.

[jjsa]

For my feeling Sections Picker is a "work around" module and there are some (human) logik problems related to it.

My approach is different, I assume that a block is more or less the same as a page. The major difference is that a global  don't really need menu links.

If we add within the info file a menu entry for example:

Code:

$menu[2] = 'Block':

we can tell that a new page we create is assigned to the Block menu which will not really exist.
We can after this, with a simple function get and insert them into the document with an includes function or a snippet:

Code:

<?php
function get_block($name)
{
global $database;
$content = "";
$sql  = "select content from ".TABLE_PREFIX."mod_wysiwyg";
$sql .= " where page_id in (";
$sql .= "  select page_id from ".TABLE_PREFIX."pages";
$sql .= "   where language='".LANGUAGE."'";
$sql .= "    and menu_title='".$name."'";
$sql .= " )";
$result = $database->query($sql);
if ( $result )
{
$row = $result->fetchRow();
$content = $row[0];
}
echo $content;
}
?>

Within the template we may have a line as:

Code:

<?php show_block('myGlobalBlock');

The name of the block (myGlobalBlock) is the menu titel we entered while creating the page. We use a name and not an ID because this is more meaningfull for human people. If we have a multilingual site we can more easelly get the correct content.

[Ruud]

A new version is released today.

It is fixing the problem of larger websites with a couple of 100 pages.
Loading the section_picker took a long time (upto 30 seconds).
With this fix this will be reduced to just one or two seconds.
The fix was made by Sare a few months ago. Many thanks for that.

A second fix makes that the full list is only created once when there are multiple section pickers on a page.

Both fixes will make working with the section picker more friendly on large WB sites.

The new version (0.26) is updated in the first post of this topic.

Ruud

[TN]

Please can you include in your code that the fields 'publ_start' and 'publ_end' from the table 'section' are checked against the actual date?
So only sections will appear that originally also appeares (depending on the dates in that fields).

[Ruud]

In normal use I would think you want to use the start/end settings in the section you use to include any other data.
It is not that hard to fix, so I made a version of the section_picker view.php that should check the linked start/end.

I did not test this, so let us know if this worked for you.
A future version might have an extra setting to enable this feature.

Unpack the zip file, and replace the view.php with the one in your current section_picker.

[dbs]

nice one, it works. *thumbs up*

[TN]

I did not test this, so let us know if this worked for you.

Hi Ruud, thanks for this coding, it works nice. Sorry that it takes such a long time to test it.

[testseher]

Vielen Dank für dieses Super-Modul.
Es lohnt sich aber auf jeden Fall die neuste Version zu installieren und damit eine vorhandene ältere, viel schneller zu machen!

[Xagone]

Hey Ruud, this addon is the MUST HAVE in any install of Wb.

BUT, found little bugs that need checking.

There is some php tag not open properly (<?php)  some are just (<?) witch could broke in a server that does not allow it.

do a search in your file for <? (with a space at the end)

[Ruud]

Did you use the version in the first post of this thread?

There have been some versions (first modifications by Aldus) that were missing the <?php open tags.
The current version (0.26) should not have these problems.