GOwin:

I have tried and tried in my two machines to replicate the error, so far without luck. Against all odds, Wordbook works as intended at least in this sense, so I'm kind of at a loss because the indicated location has nothing wrong, as you can see in you rcopy of the file...

To back-up your entries, use PHPMyAdmin and export the data for the relevant tables. This at least will save your data for a time when the module works fine for you.

Cheers --though I don't feel right now very cheerful myself...

Bulls:

Since you've already had success creating a custom block, try adding to the links the attribute+value pair target="_self". Haven't tried it, but this might do the trick.

Cheers.

GOwin:

I haven't seen what you report about links. So far the only attention I had given to the subject was the URL field, in which you only type the URL and it gets converted to a link instead of being displayed as text (this is accomplished using the function makeClickable).

Let me check on this. Take this into account: any textarea is sanitized using displayTarea, a function that, depending on the value of the relevant variables ($html, $smiley and $xcode) calls other functions to transform the text. Since Wordbook works by default with all values set to "1", if you have bbCode it will be translated to HTML for display purposes (your browser doesn't "speak" bbCode).

There's one thing that happens in the sanitizer: line 287 reads:

$text =& $this->makeClickable($text);

Since this is outside any conditionals, I interpret it as meaning that all text passes through the makeClickable function. This function (lines 130-135), in turn, searches for strings that might seem as links, so my guess, without having tested it, is that you don't need to write actual < a> tags in the text, but just write the link and it will be converted. The problem with this is I don't know if this will let you then edit the text. It's worth trying, though, and the certain thing is that the function displayTarea is here to stay.

As to your comment about the module's name, the variable used is the directory because if you change the name of the module but it still resides in the directory Wordbook, you need to be able to access it. You'd need to change the install directory. In this I'll try, in the future, to follow the logic explained by daigoro in another very interesting thread about cloning modules, but for the moment that's the way it's set. Sorry.

As to images, you should be able to use them following my comments here. The problem is that the image will appear also in the block. I read Catzwolf has a solution for this, a summary function that strips the text from links and images to show just text in the teasers. I'll look after that code and if possible will implement it so that only the actual definition shows images.

This is for the moment what I can say.

Cheers.

riorben:

There's been a tenacious problem with the blocks in Soapbox because of the group permissions. However, I think I have fixed it for good. I'm now in the process of making the final testings for a more stable version of Soapbox. If we're lucky, it won't take longer than a couple of days before release. Please have a little more patience, and I think it'll be worth it.

Cheers.

domineaux:

Blocks edition can mean one of two things, or both:

1) Editing the PHP file that contains the functional code to retrieve values to display in the block.

2) Editing the HTML file that contains the visual structure of the data to show in the block.

Apparently you want to edit the template. Well, then please remember you can't edit the default theme. You'll never get "Save" options when trying to edit the default theme. You need to "clone" the theme, then make your clone the active theme, and only then will you be able to save changes.

Cheers.

GOwin:

Try this: openn your file modules/wordbook/blocks/random_term.php and look for the offending line, number 64. It contains a rather large string with variables.

Please try replacing

$xoopsModule->dirname()

with

$module_name

And tell us if this solves the problem...

Cheers.

marcdg:

This one is easy. Change the TR labeled "footerbar" in your theme file. There's the link.

Cheers.

Those modules will not get their strings translated to the new language. If the module is built right, they will show in english; if not, they will appear like this _MD_SOMETHING.

Cheers.

punivers:

Your image shows a right column with a background color we'll call X. This same color is defined as the background color for your right blocks.

In your theme.html file, you'll see that the right column is built using a TD tag labeled "rightcolumn".

Open your style.css file and look for the options related to this selector. You'll see there are four:

td#rightcolumn
td#rightcolumn th
td#rightcolumn div.blockTitle
td#rightcolumn div.blockContent

In the first one you'll have the background color for the whole column. In the last one, the one for the block. If you want these colors to be different, just change their values in the CSS file.

Don't forget to clear your cache and delete the files under templates_c to see the changes you've made.

Cheers.

Guerlot:

Go to System Admin > Preferences > General Settings. Then look for an option labeled "Default Comment Display Mode" and set it to Flat. Click on "Go!" to save your new setting. That's it.

Cheers.