Main changes:

• Each entry has an option to accept a trackback or not.
• To upgrade the version, you must update the module.
• Portuguesebr language files were added, thanks to leco.

Download here

http://hodaxoops.sourceforge.net/

Main changes:

• The 3rd wysiwyg editor was implimented at d3blog-1.04. It will be usefull for html writers, especially technical writers writing program codes, html ,css and so on by pre tag. Select the quicktag in admin preferences, that's all.
• Character entity reference replacement is also enabled directly in a form's textarea. Just select the part(Ctrl+C) that you want to convert and click the button 'Entity'.
• Smarty plugin d3blogCount is also added which generates entry count. A var name and filters of uid and cid are options.

Download here

http://hodaxoops.sourceforge.net/

We know we can upload photo images, but also can create thumbnails easily by an image manager with myalbum-p.
D3blog v1.02 or later enables more semantic markup of image layout with attributes of caption and cite. All you have to do is just replace "img" tag to "fig" tag.

Markup by [fig] and [sitefig]

[fig alt="value" credit="value" title="value" caption="value"]image url[/fig]

makes those markup:

<div class="figure value-of-align">
  <img src="image url" alt="value of alt" />
  <p class="credit"><abbr class="type" title="Photograph">Photo</abbr> by <cite>value of credit</cite></p>
  <p class="caption"><em class="title">value of title</em>value of caption</p>
</div>

Without credit, title, caption, then more simple markup.

<div class="figure">
  <img src="value of fig" alt="value of alt" />
</div>

Any element and any order of attributes will do.

NOTICE: alt is special

When you choose a simple markup without credit, title and caption, "alt" attribute must be filled.

[siteurl] and [sitefig]

shorten urls of image, just a relative path excluding xoops_url without prefix '/' which make us free from moving site.

Remember that minimum one attribute is required.

How do we get an image markup with hiper text? That is simple, too.

[url=link url of image][fig align="value" alt="value" credit="value" title="value" caption="value"]image url[/fig][/url]

will make:

<div class="figure value-of-align">
  <a href="link url" title="value of title"><img src="image url" alt="value of alt" /></a>
  <p class="credit"><abbr class="type" title="Photograph">Photo</abbr> by <cite>value of credit</cite></p>
  <p class="caption"><em class="title">value of title</em>value of caption</p>
</div>

Now, make a practice.

SpringLorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat.

Left image's xoops code are:

and will be:

<div class="figure">
  <a href="http://www.kuri3.net/uploads/photos1/9.jpg"><img src="http://www.kuri3.net/uploads/photos1/thumbs1/9.jpg" alt="" /></a>
  <p class="caption"><em class="title">Spring</em>Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat.</p>
</div>

Notice that "figure" class has a default value of float style, float:left.

Next is a sample of right floated image.

Photo by hodaka

SpringLorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat.

This is full of fig attributes. An alt attribute is not neccesary with a caption attribute.
This comes from:

[url=http://www.kuri3.net/uploads/photos1/9.jpg][fig credit="hodaka" align="right" title="Spring" caption="Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat."]http://www.kuri3.net/uploads/photos1/thumbs1/9.jpg[/fig][/url]

and converted to:

<div class="figure figright">
  <a href="http://www.kuri3.net/uploads/photos1/9.jpg"><img src="http://www.kuri3.net/uploads/photos1/thumbs1/9.jpg" alt="" /></a>
  <p class="credit"><abbr class="type" title="Photograph">Photo</abbr> by <cite>hodaka</cite></p>
  <p class="caption"><em class="title">Spring</em>Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat.</p>
</div>

NOTICE: target

We don't use target="_blank" which is not recommended any more for an accessbility.

Attributes and property of [fig], [sitefig] tag

property of "align" left|center|right

"center" and "right" creates "figcenter/figright" class. We just have to prepare styles sheet for them. See samples of style sheet below.

property of a alt attribute alt

makes a value of an attribute alt. must be proceeded and follwed by ' or ".

property of "credit"

makes a value of cite. must be proceeded and follwed by ' or ".

property of "title"

shows a title of image. must be proceeded and follwed by ' or ".

property of "caption"

will be a description of image. must be proceeded and follwed by ' or ".

Style sheet

Below is the sample of style sheet. You may customize a div width or an image width along to your theme. IE, not compatible for seudo class, might need some spaces after an title.

/* default */
.figure {
  clear: both;
  margin: .3em .3em 1em 0;
  width: 160px;
  float: left;
}
.figure.figcenter {
	margin: .3em auto 1em auto;
	float: none;
}
.figure.figright {
	margin: .3em 0 1em .3em;
	float: right;
}
.figure p {
  margin: 0;
  width: auto;
}
.figure .credit {
  font-size: .8em;
  text-align: right;
}
.figure .credit cite {
  font-style: inherit;
}
.figure .caption {
  font-style: italic;
  font-size: .9em;
}
.figure .title {
  font-style: normal;
  font-weight: bold;
}
.figure .title:after {
  content: ":";
}

FigureHandler

With a figure handler preference on, the javascript automatically applys a class to the image div that corresponds to the percentage of the column width the image takes up.
Arrange a parent node width corresponding to your theme. See for more details: A List Apart -- If I Told You You Had a Beautiful Figure...

Download d3blog

latest d3blog at sourceforge.net

4. Updateping and trackback ping

1) Sending a weblog updateping

Cofigure the weblog updateping servers in the preferences.
Will not send, by default, if updateping checkbox is off.

2) Send a trackback

Fill the outbound trackback textarea, each url must be seperated by line break.
The trackbacks can't be sent again unless they are deleted.

autodiscovery of trackback url

Check autodiscover checkbox, then will fetch trackback url automatically.

3) Receive a trackback

Give read permission to guests.
Trackback approval is also vailable. Cofigure the preferences admin.

4) Against trackback spams

Cofigure those in the preferences admin:

(a)reject trackbacks with no title or blog name(by default)

(b)banned words

reject if trackback contains a banned word in a title, a blog name and an excerpt. each words must be seperated by a line break.

(c)DNSBL check

reject if sender's address is registered as a spam in the blacklist.

(d)SURBL check

reject if urls in an except are registered as a spam in the blacklist

(e)multibytes characters check

Valid only when XOOPS_USE_MULTIBYTE is on.
will check utf regex pattern of characters and character lengths needed.

(f)regex pattern

(g)references check

fetch sender's contents and check if they are sure to refer to my blog url.

5) When you choosed trackback ticket, remember that:

• a sender must keep javascript on
• a sender must re-get after a ticket expiraion, 1day
• a sender can't re-use the ticket
• a sender can't use a formal trackback url in an embedded rdf.

* Not recommended as this ticket system is outraging general trackback rules.
* More effective are approval system or article 4 stuffs. The ticket system should be the last resort of anti trackback.

5. Entry-by permission control

You can control a privilege of each entry. Just configure the permitted groups by default in the preference admin. Remember that this won't give any privilege to the groups unless they are given the view privilege by the permission manager.
Even forbidden groups can read a title and an excerpt if configured to be yes in the preferences admin.

ATTENSION

Permitted groups in each entry must be renewed by phpMyAdmin if you added new groups or get re-started entry-by permission control.
Once you added new groups, be sure to update the module and configure the default groups. In version 1.02 or later, new groups are automatically included to the default groups only if all the groups were chosen as the default groups.

6. Plugins

Upload plugins under the "extra" directory. Some are required to be renamed.

module name	plugins	remarks
xmobile	extra/html/modules/xmobile/plugins/d3blog.php	rename dirname.php see 1*
piCal	extra/html/modules/piCal/plugins/ monthly/d3blog-date、d3blog-entry
d3pipes	extra/xoops_trsut_path/modules/d3pipes/joints/ block/D3pipesBlockD3bloglist.class.php	No need to upload when Hodajuku distribution.

These are automatically included in d3blog.

module name	plugins	remarks
d3forum	xoops_trust_path/modules/d3blog/ class/d3blogD3commentEntry.class.php	for comment integration see 2*
search	xoops_trust_path/modules/d3blog/ include/search.inc.php
whatsnew	xoops_trust_path/modules/d3blog/ include/data.inc.php
waiting	xoops_trust_path/modules/d3blog/ include/waiting.plugin.php

1* if appendix is numeric

search 108th line and modify xmobile/class/Control.class.php.

if(preg_match("/(^\w+)\d$/", $this->pluginState,$matches) && !file_exists(XOOPS_ROOT_PATH."/modules/$this->pluginState/mytrustdirname.php"))

2* d3forum comment integration

Cofigure the format for comment-integration textbox when creating a new forum like this:

public-side dirname::d3blogD3commentEntry::trust-side dirname

7. Wysiwyg editor

FCKeditor is limited to the groups allowed to use html.

Download the core library from Package_hd for XCL2.1 of Hodajuku Distribution site.

Upload the core library to html/common/fckeditor directory.

8. Image

You can upload images by a xoops image manager or myalbum-p. D3blog image uploader is in TODO lists.

9. d3forum comment integration

All you have to do is configurate the d3forum modulename and forum_id in the preferences admin. No need to modify the template any more. (version1.02.1 or later)
To upgrade from an older version, update the module and some templates. Be sure that the d3forum was installed and the corresponding forum_id was set in advance.

Notice:

Upgrade d3forum to V0.83 or higher. Don't fail to upload "d3comment" smarty plugin either.

10. to clone a block

Prior to v1.02, all the blocks are clonable. As of the latest entries block, the clone can have its own template if only a template name is given by editing the clone as followed:

db:dirname_blocks_original-name.html

Put the corresponding template under trust/templates and register it in db, meant by module updating. A file template which starts with 'file:' must be written in an absolute path.
If you put the template below templates directory under the active theme, no db registering is required.

templates under the theme

They are given the first priority if their last modified datetime are newer than cache's.

Have fun.

How to use fig tag

]]> http://labo.hodaka.org/modules/d3blog/details.php?bid=3 2008-05-10T16:30:00+09:00 2010-06-24T00:28:18+09:00 hodaka

Here are things to do before you start.

Here are things to do before you start.

1. Configure the admin settings right after installing

1) Preferences

Details are followed.

2) Create categories

One or more categories are required.

3) Give the permissions to each groups

Even administrators can't do anythig if they are not given any permision.

The "editor" is almighty. Only the editor can edit other's blog entry.

"Html allowed" privilege should be limited to the trusted people. It will cause serious problems if opened to anonymous.

Can't control category-by permissions. Clone d3blog module if you need.

4) Blocks/Module Perimssion/Language manager

Those utilize altsys module functions. Must configure at least module access permissionaltsys.

All blocks are clonable. Two types of blocks, list or table, enable to make cosmetic changes which can be done by editing templates or styles.

5) CSS manager

(A) Non dynamic css which can be configured by prefences

First, on the public side, give 777(read/write/execute) permissions to the css directory, 666 to files under the directory.

Second, write down external css files by css manager.

After writing down css files, change permission back to 644.

Rename .htaccess.dist to .htaccess if possible.

In case a module name is not d3blog, don't miss to write down external block style files, or it will not be valid.

(B) Dynamic css

This will be very helpfull to modify styles. Configure preferences whether yes or no.

6) Templates manager

Altsys module function is enabled.

Style sheet templates are also available.

Here we are ready to start.

2. Import from weblog-1.42, weblogD3, xeblog and d3blog

Importable are:

1. table data of categories, entries, trackbacks
2. comments and notifications
3. synchronization of comments and trackbacks

Remember that comments and notifications data are not recovered to the original module once they are moved. On the other hand, table data are kept live after importing, just copied.

3. Approval manager

Can get a whole view of the entries or trackbacks to be approved. You can accept or delete whole or each of trackbacks.

Notifications or installing a waiting module are recommended.

To How-to-configure(2)

]]> http://labo.hodaka.org/modules/d3blog/details.php?bid=2 2008-04-19T16:00:00+09:00 2010-06-24T00:28:39+09:00 hodaka

How to install of d3blog are those:

How to install of d3blog are those:

1. Packed are:

|
+-- extra	here are plugins
|   (xmobile and piCal in html)
|   (d3pipes in xoops_trust_path)
|
+-- html
|
+-- xoops_trust_path

2. Make a directory for XOOPS_TRUST_PATH.

• Edit mainfile.php and define XOOPS_TRUST_PATH dir.


• You are supposed to get accustomed to D3 type module.

3. Install altsys module(v0.55 over).

4. Upload files to a server.

• Rename module dir name as you like.


• Copy modules as much as you need.


• Edit root/mytrustdirname.php if you want to change a trust-side dir name.


• No problem with plural trust-side dirs.

5. Install a module as usual.

== UPGRADE ==

d3blogv1.00 => v1.01

• Delete all the d3blog files in both root-side and trust-side before uploading.


• Update a module.


• See if "trackback spam check" are OK'ed in the preferences.


• Re-construct "permission management" table so as they were fully changed to be more simple. See HOWTO 1-3)Privilege.


• Templates are required to update.



$currentUser.perm_name.xxxx => $currentUser.user_perm.xxxx




Related templates:

inc_entry.html, main_submit.html



• Also required to update so as Smarty plugins were renamed.
  

  mb_truncate => xoops_mb_truncate 

  
  

  Related templates:

  admin_approval_manager.html, main_details.html, main_submit.html



• Again, main_submit.html is reqired to update.
  
  Add this on the shoulder of trackback url textarea.
  

  name="autodiscovery" id="autodiscovery" value="1"<{if $form.autodiscovery_}> checked="checked"<{/if}> /><label for="autodiscovery"><{$smarty.const._MD_D3BLOG_LANG_AUTODISCOVER}></label> 

  
  


• Modify names of included files which were renamed.
  

  renamed templates are:

  main_header.html => inc_header.html, main_entry_html => inc_entry.html, main_comment_form.html => inc_comment.html

  
  

  templates to be modified:

  main_archives.html, main_comment_edit.html, main_details.html, main_index.html, main_submit.html



• Modify multibytes regex for spam check if youb use multibyte language.
  
  Replace the pattern like this (for Japanese):

  [一-龠]+|[ぁ-ん]+|[ァ-ヴー]

]]> http://labo.hodaka.org/modules/d3blog/details.php?bid=1 2008-04-17T15:48:35+09:00 2010-06-22T21:01:24+09:00 hodaka

Multi languages site for d3blog discussion has lanched. Join us and contribute to hodaxoops project, bug reporting and Q&A etc.

Multi languages site for d3blog discussion has lanched. Join us and contribute to hodaxoops project, bug reporting and Q&A etc.]]>