Calling files in a plugin

[FSGDAG]

I'm trying to create a plugin from what was a mod before. The mod has two files that it needs to run correctly... Example :

block.file_one.html
block.file_two.html

Then you output the data by saying

<%block_file_three title="" max_item="6" listing_type="sponsored_premium" template="block.file_one.html" template_rows="block.file_three.html"%>

What I'm not sure about is how to call file_one and file_two.

[echo@]

Im not 100% sure what it is your wanting, but I guess you want to convert a block to a plugin?

[FSGDAG]

Yep!

[Bruceper]

You might be best off waiting for Nakos to give you an answer on this one.

[mpdaddy]

I am not sure what you want either, but does this help you?

$file2 = file_get_contents($indexu->config['plugin_path'] .'/plugin_name/template/file2.html');
$file3 = file_get_contents($indexu->config['plugin_path'] .'/plugin_name/template/file3.html');

$tpl->assign("file2",$file2);
$tpl->assign("file3",$file3);

$plug->SetHtmlHook(whatever_hook_you_want, file_get_contents($indexu->config['plugin_path'] .'/plugin_name/template/file1.html.html'));

Hopefully you can figure that mess that I wrote. I will have more time to help in the morning when I get off work.

Regards
mp

[echo@]

Yep!

Dont take this the wrong way but why re-invent the wheel?

FSGDAG do you see the time when indexu will neither need a block system?

Do you think or would want the plugin system to take over for blocks completely?

[Bruceper]

I could picture the blocks being plugins, but they would still be blocks. And they would be plugins so you don't need to edit pages to enable/disable them. Of course to change anything in them you would still edit the block.

[FSGDAG]

Thats basically what my thinking was... With it being a plugin your not constrained as much as if it was a MOD. Would it be good if IndexU could go completely MODless and everything a plugin... Hell yes! LOL But I'm not sure that will happen. But at this point my rule of thumb is, the more plugins and less MODs the better!

[echo@]

I dont consider blocks as mods. Blocks are blocks

Unless you can have the block php and html packaged in an plugin directory as opposed to the block directorys, you have still got to remember to backup them to.

Also I think in the backend plugins could be grouped under expandible folders depending there group.
Personally I think the plugin area is quite disorganised, if people were thinking of adding block plugins (or Blockins ) it would be hard to find each one and you'll probally have a page as long as your arm.

[mpdaddy]

I agree with echo, somewhat. I think there should be a system similar to the plugin system where you can install and uninstall blocks without editing a file, like installing and uninstalling a plugin. And, cusom blocks ccould be made and uploaded to the blocks directory.

I like the idea FSGDAG has about making a block a plugin. It is the solution for now. That way you can turn them on and off at will. You can make a block a plugin though and it will work just fine.

Hopefully I worded that all O.K.

Regards
mp

[Bruceper]

Give us time, perhaps we'll convert all blocks to plugins AND find a way to organize them better.

[nakos]

hello,

i think you dont need to make blocks, because you could make a function or mod or block in a plugin.

you could call other files from plugin.