Spartacus, anyone?
![Smile :-)](./images/smilies/icon_smile.gif)
Great plugin!
Best regards,
Garvin
Unfortunately, yes. I don't know enough about regexps and string handling to fix that1. Am I right that [DTR]My'stuff[/DTR] the ' character could make problems in the evaluated regular expressions?
Yeah, for the long run this would be more ideal. But maybe for the time being we could rely on the spamblock plugin? *g*Ideally, we could have a standard font folder (maybe as a subfolder of the uploads?) that ALL such plugins, (captha, this one, and the one Carl referred to) can use. It would also be nice for the application to provide a variable to that real path.....2. Maybe it would be nice to make the plugin be able to read the TTF files bundled with the spamblock plugin? So you would not need to bundled the Vera*.ttf files with the plugin as well - because that makes the plugin a whopping 500kb download.![]()
Alernately, the plugin could be modified to let the user enter their own path....
Is there a function to return the plugin path? I had to use the app root and then append /plugin/serendipity_event_dtrmarkup/ but as you point out, that won't always work...4. You use a hard-coded "plugins/..." path to access the 'dtr.php' file. In some environments (like mine) the spartacus plugins get put into an "additional_plugins" folder, so this would not load the right PHP file. The best way would be to make the HTTP path to dtr.php configurable, so that I could fix that on my installation. The default could then be the string you are currently using?
Code: Select all
$link = $serendipity['baseURL'] . ($serendipity['rewrite'] == 'none' ? $serendipity['indexFile'] . '?/' : '') . 'plugin/mycustomname';
Uh, ah...I'm afraid I don't understand the question. Which piped contents do you mean?1) Is there a way to get the piped content to show up at the end in the backend configuration? Right now it is in the middle for some reason...
That is pretty hard to do, like preventing all image leaching. There are only two ways that really work:2) Is there a way (if 5 is done) to make the image generation scrip only work if called from the blog itself? I wanted to prevent a direct external call (like image leaching)
Good question. Since cached images only represent replacements that usually are always contained and always recreated (even through googlebotr or whatever) I don'T believing purging the cache will do much good.3) is there a need to manage the size of templates_c? This could chew up lots of space, and it might be good to purge the cached files occasionally....
That would simply be $serendipity['serendipityPath'] + "templates_c" or + "plugins". Both directories are not allowed to be called differently. Instead of prefixing serendipityPath you can also prefix $serendipity['baseURL'].Also... What are the serendipity variables to build guaranteed paths to templates_c and to the plugins directory?