Forum Replies Created

Viewing 15 replies - 16 through 30 (of 37 total)
  • Thread Starter Raphael

    (@akerbos87)

    I just realised that actually most style is implemented using css classes that are provided nowhere, so users can edit their style to accomodate their needs. Sorry for my hastiness; I had only noted the lack of a css file earlier.

    This is definitely better than hardcoding but such changes can be lost during style upgrades.

    What is hardcoded, though, is the way how you separate entries from footnotes. This should definitely put into users’ hands.

    Also, please move your setting(s) from WordPress Settings to a separate page. Afaik it is considered (very) bad style to pollute WordPress administration pages; can’t find a reference now.

    Plugin Author Raphael

    (@akerbos87)

    Of course you can! Just add a text widget with the shortcode (and maybe layout code) you want.

    You have to enable shortcodes there, that is add

    add_filter('widget_text', 'do_shortcode');

    to a reasonable place where it gets executed before widget construction. functions.php might be a good place, just remember to repeat it after upgrades.

    Plugin Author Raphael

    (@akerbos87)

    I would not expect [zenalbum] or [zenlatest] to work since they rely on json.php.

    It should be too much trouble for you to fix the URLs produced for [zenimage] and [zengallery], though. Indeed, ZP 1.3 did not have that album/ part. Just go to the following places and adapt according to the URLs you need:

    gallery.inc.php ll 114-125 (link targets)
    zenphoto_gallery.php l 470 (image url)
    zenphoto_gallery.php l 508 (image url)

    If you let me know what has to be there (have no ZP 1.4 myself currently) I am happy to publish it as a patch.

    However, it might be while until I really upgrade the plugin to ZP 1.4, unfortunately. Making it support both versions simultaneously is a bit harder than just fixing the paths, and I want to do it together with some other changes. And, obviously, I got other things keeping me busy.

    Plugin Author Raphael

    (@akerbos87)

    Ok, the forums do not handle combinations of backticks and code tags properly…

    Plugin Author Raphael

    (@akerbos87)

    json.php has nothing to do with WordPress. It has to be in the root of your Zenphoto installation as explained in the documentation and the file itself. But it will most likely not work with ZP .4, anyway.

    I have no idea where the code tags might come from; that has nothing to do with the wrong ZP version and is not a problem with WordPress 3.1 in general (since it works for me). Please check in TinyMCE’s HTML editor that you do not include those yourself with the WYSIWYG editor.

    If you want to post HTML here so that we can see it, please enclose it in backticks like so: ... (as proposed right below the textbox you enter your message into). If you reread your own posts, you notice that the tags have “vanished” so I could not see what you were referring to.

    Btw, your Zenphoto installation only says “setup scripts missing” so how you can expect an external plugin to retrieve pictures from it eludes me.

    Plugin Author Raphael

    (@akerbos87)

    > I have the same problem.
    Are you referring to the other thread over here?

    I am not sure how to read your post. Is this a fix, that is do you offer some modification to json.php that works with ZP 1.4 (but not with 1.3)?

    As for your PS: please post the complete URL the plugin generates and the one you get if you open this picture in Zenphoto 1.4? It is possible that the way URLs are assembled changed (that should cause all generated links to images to break, by the way).

    Thread Starter Raphael

    (@akerbos87)

    There are no options I am aware of, what are you referring to?

    Thread Starter Raphael

    (@akerbos87)

    I have implemented this feature; where can I direct the patch to?

    Also, how is your move to bib2tpl coming along?

    Let me propose some more changes.

    As far as I know, (top level) shortcodes are evaluated from left to right. That should enable you to improve bibshow, namely remove the nesting. Create a shortcode [bibload] that fills the cache with data. All [bibcite] after that can access the data now. A code like [bibliography] can later print the list of used keys. (Names preliminary).

    Citation marks like [1] should be links to the resp anchors, placed in the bibliography. Backlinks to citation point from bibliography entries are possible, but imho not necessary.

    Enable [bibcite] to handle multiple keys; [bibcite key=A,B] should result in [1,2].

    I plan installing ZP 1.4 myself sometime over the next weeks. So long, if you posted the content of the .htaccess here, I might be able to figure something out.

    Plugin Author Raphael

    (@akerbos87)

    Version 2.1 will give options to style image boxes (and captions, too). Coming soon.

    Maybe you have to add a new rewrite rule for treating requests for json.php in the same manner as those for rss.php?

    In the ZP 1.4 release notes, it says that with mod_rewrite and the new .htaccess, old RSS links should work. Can you check that you have that set up?

    When does this exception/warning occurr? When you use zenalbum or zenlatest? Everything else works?

    Wow, ok, ZP 1.4 seems to change some things significantly. I will have to do the following things

    * Install ZP 1.4
    * Check wether 1.4 and 1.3 can be accessed in a compatible way
    — If so, implement that
    — If not, make Zenphoto Gallery handle both (by setting?)

    Right now, I do not quite have the time for that, sorry. If you can provide a temporary workaround (i.e. a json.php that offers the same as the one I built but works with 1.4) I would be happy to include it.

    I will fix it eventually, but only when I have a day or two to spare for it.

    By the way, do zenimage and zengallery work?

    Plugin Author Raphael

    (@akerbos87)

    Sorry for the very late answer; I did not realize that the plugin owner is not notified of messages here.

    Thank you very much for this report. I will include a fix in a future release.

    Plugin Author Raphael

    (@akerbos87)

    Sorry for the very late answer; I did not realize that the plugin owner is not notified of messages here.

    I assume you read entry “How do I get rid of those boxes?” of the FAQ. Note that without knowing what you changed I can not help you specifically.

    However, the FAQ give vital hints. You can
    a) Change class wp-caption in your theme’s CSS without changing the plugin
    b) Put another class in the plugin’s source as stated and define it in your theme’s CSS
    c) Put inline CSS in the plugin’s code

    Note that this issue has been identified as a weakness and will be fixed in a future release.

Viewing 15 replies - 16 through 30 (of 37 total)