hackblog@wonderwinds

Yesterday I only got a 404 lady. Let's see what you have brewed today

@A: 404 from the link I sent to the evoteam? I didn't test the link so I reckon I just screwed up typing ... yeah that was it. File name is "visiglyph_plugin" but I typed "visiglyphs_plugin". My bad.

@Y: My form?!?!?! You mean THE form still defaults to "embrace spam". Maybe someone on the developers team oughta do something about that ... ?

Yeah I gotta get back to all sorts of little details like that. Another one that I've already started on is fixing gross flaws when you "view source". Do a raw installation with sample posts and you'll see that the entire sidebar is located on ONE line in the source code. um ... got "\n"?

Okay cool. I think. So what you're saying, if I understand correctly, is this:

If your blog is in a folder AND your $baseurl (set in conf/_basic_config.php) has something like "domain.com/folder" then you don't need to edit a file OR make a plugin setting.

On the other hand, if the path to the installation is NOT the same as your $baseurl then you probably will need to edit a file AND set the appropriate plugin setting.

Actually that ain't right either. My test installation is in a folder, and for that installation my $baseurl knows about the folder, but the plugin didn't work if I didn't hard-code the folder name into the class file.

Hmmm... Aha? sub.domain.com versus domain.com/sub could be part of it. Another aspect I was just thinking of is when you use one host for multiple domains. TECHNICALLY the add-on domain is in a folder for the "primary" domain name, but as far as the URL is concerned it is in the root folder.

So I wonder if you'll do a test for me. Instead of visiting your sub.domain.com could you go to domain.com/sub/ and see how it works? If you go to your admin area that way you'll probably have to log in again. Oh and b2evo will probably keep throwing you back to $baseurl. Anyway if you try it via the back office you'll have to have a new randomizer and not visit the tools tab until you have the full url showing .com/sub/ to see if it's working that way.

I think you'll find it won't work that way, which means my readme needs to point out that there are conditions under which you will need to set the back office setting AND edit the file. I'm also thinking of getting rid of the back office setting. If you have to edit one file then it's no biggie to have to edit another eh?

I just found out the visiglyph preview does *not* work in the new setup.

Why can't you make the plugin find the files? I did it with $plugins_path in the chessboard render plugin.

Your last suggestion for the help file is ok. I'd give an example like:

If you have a folder path in your $baseurl (yoursite.com/blog/) then you need to hack a file and set a setting.

Did O mention the preview doesn't work in the new setup? Errors all over, like:

Warning: imagepng() [function.imagepng]: Unable to open '/home/hemmi3/public_html/plugins/visiglyph_plugin/visiglyphs/7774d07bcf86c2353d7b9a7611a93c4e.png' for writing: No such file or directory in /home/hemmi3/public_html/blog/plugins/visiglyph_plugin/_visiglyph.class.php on line 159

Keep up the good work.

function GetDefaultSettings()
{
global $plugins_path;

return array(
'image_path' => array(
'label' => T_('Path to images'),
'type' => 'text',
'size' => 50,
'defaultvalue' => $plugins_path.'chessboard_render_plugin/images/',
'note' => T_('Change this path if you have another set of images or have them stored in a different location. Don\'t forget the trailing slash (/).'),
),
);
}
and
function RenderItemAsHtml( & $params )
{
/*
* Get user input for image path (or default = /plugins/chessboard_render_plugin/images/)
* Next, set Global variable $chessboard_image_path
*
*/
$tempImagePath = $this->Settings->get( 'image_path' );
$chessboard_image_path = chessboard_image_path( $tempImagePath );
In the Chessboard render plugin the path is meant to be editable for some stupid reason like the coder (that's me) liked to have a setting for his plugin. But the idea is there.

I like the chessboard plugin. Great work!

Okay so previews work for logged in people only (but not in the zip file), and both "cookie me" and "spam me" are off by default.

I'm late for work

You should use relative paths to make things easier

'label' => T_('Relative path to images'),
'type' => 'text',
'size' => 50,
'defaultvalue' => 'images/',

.....

$image_folder_path = dirname(__FILE__).'/'.trim( $this->Settings->get( 'image_path' ), '/' ).'/';
$image_folder_url = $this->get_plugin_url().trim( $this->Settings->get( 'image_path' ), '/' ).'/';

¥

ps - yer blog doesn't want to remember me .... and no more porn spam

I don't know if it will work with 1.10.* or not, but my gut tells me it will. It worked nicely with 2.1.0 but now there is a 2.2.0 out, so I focused upgrades on that version. When I publish that new version the same thing will be true: it will probably work in 1.10.* but I can't say for sure because I didn't test it in that environment.

If you have a 1.10.* installation and try this plugin please let me and the rest of the world know if it works or not for you.

(Note to self: since 1.10.3 is the latest stable release shouldn't you be looking at plugins that work in that version?)

Interesting. So after you make a change to the settings and make a new comment (from out in public) you get the visiglyph that the tools tab says is for a different configuration?

It won't re-do a glyph, so existing comments won't update, but new comments should get the new visiglyph. I've already upgraded my own installation, but I'll grab my own zip file and email you with some code to add to your plugin so we can test what's going wrong.

(Note to self: change the visiglyph size here to one size smaller...)

I second that it works in 1.10.3, and that the issue has been resolved. Thanks for the swift reaction!