Ok, first things first: PEOPLE WITH THE TINYMCE PROBLEM, PLEASE READ HERE! I'm talking about the problem many of you reported on this thread (EdnaGarrett, miriam, digits & others) producing error messages on the `file_get_contents` function. After digging a little in the WP code, I think the problem may be related to the PHP `realpath` function, which is buggy on some systems. If this is the case, the issue is related to WORDPRESS (not ZenPress) and I'm sorry to say you'll have to wait for a fix from the WP team (hopefully in the upcoming version 2.1.3).
And now, for something completely different: thinkdreams, I fixed the `urlencode` issue with the function you suggested, and the fix will be in the next ZenPress version. In the meantime, I hope trisweb will be so kind as to give me his permission to use his piece of code in my plugin
Thanks Simbul -- you can definitely use my code ;-) It's GPL'd!
We also need to start talking about integrating this into the Zenphoto project, with further wordpress support like random image display, etc, starting to be included into one common plugin. Sound good?
Simbul wrote: If this is the case, the issue is related to WORDPRESS (not ZenPress) and I'm sorry to say you'll have to wait for a fix from the WP team (hopefully in the upcoming version 2.1.3).
I came to the same conclusion. Let's hope the WP 2.1.3 will fix it.
> Thanks Simbul -- you can definitely use my code ;-) It's GPL'd! > > We also need to start talking about integrating this into the > Zenphoto project, with further wordpress support like random image > display, etc, starting to be included into one common plugin. Sound good?
I would like to use lightbox, but it would take forever to edit every thumb I insert to include rel="lightbox". Is there a way to modify the zenpress code so that it automatically inserts the lightbox tag when the thumb is inserted?
@Simbul: Well, I still can't figure it out. All the other options seem to be found but that custom zenpress_custom_height and weight. It has something to do with the default. My settings were empty in the config for those and somehow because of that it went to get them in the zp database. Something odd is at bay there.
Additionaly, zenpress is not compatible with sub-albums (with mod_rewrite) as it is. I was able to make it work by removing the url_encode for the mod_rewrite style image URLs. It seems to work fine even with album names that have spaces in them but I haven't done extensive testing.
The second part of your question is fairly easy to solve. If you look about six or seven posts above, you'll note that the subalbums thingie was fixed using pathurlencode and will be releasing soon in a new zenpress version. In the meantime, just replace urlencode with pathurlencode in your zenpress files (you already know where it looks like) and it should work fine. pathurlencode is a built-in zenphoto function. You can remove it as well, but I don't know what effect that will have on every possible variation in album names.
@edasque, my guess is some variable naming conflict, with Zenpress using a var name like `$table` or something and it overwriting one for WP. Simbul will have to take a look through the code and check for that...
Comments
Ok, first things first: PEOPLE WITH THE TINYMCE PROBLEM, PLEASE READ HERE!
I'm talking about the problem many of you reported on this thread (EdnaGarrett, miriam, digits & others) producing error messages on the `file_get_contents` function.
After digging a little in the WP code, I think the problem may be related to the PHP `realpath` function, which is buggy on some systems.
If this is the case, the issue is related to WORDPRESS (not ZenPress) and I'm sorry to say you'll have to wait for a fix from the WP team (hopefully in the upcoming version 2.1.3).
And now, for something completely different: thinkdreams, I fixed the `urlencode` issue with the function you suggested, and the fix will be in the next ZenPress version. In the meantime, I hope trisweb will be so kind as to give me his permission to use his piece of code in my plugin
That's all folks!
We also need to start talking about integrating this into the Zenphoto project, with further wordpress support like random image display, etc, starting to be included into one common plugin. Sound good?
I came to the same conclusion. Let's hope the WP 2.1.3 will fix it.
Groeten, this time from Las Vegas, Miriam
Nope. You don't have to have zp and wp on the same database. I've got mine running on two separate mysql DBs and it works fine.
They can be if you want, but then you get into messing with prefixes, and it gets confusing....
WordPress database error: [Table 'zenphoto.wp_options' doesn't exist]
SELECT option_value FROM wp_options WHERE option_name = 'zenpress_custom_width' LIMIT 1
WordPress database error: [Table 'zenphoto.wp_options' doesn't exist]
SELECT option_value FROM wp_options WHERE option_name = 'zenpress_custom_height' LIMIT 1
This is a screen grab of the SQL errors and empty thumbnails:
http://www.generalmagic.org/gallery/albums/Others/Linked To/zp_error.jpg
(WP 2.1.2 with Zenpress 1.2.2 and ZP 1.0.8.2)
> Thanks Simbul -- you can definitely use my code ;-) It's GPL'd!
>
> We also need to start talking about integrating this into the
> Zenphoto project, with further wordpress support like random image
> display, etc, starting to be included into one common plugin. Sound good?
sounds VERY good!
Additionaly, zenpress is not compatible with sub-albums (with mod_rewrite) as it is. I was able to make it work by removing the url_encode for the mod_rewrite style image URLs. It seems to work fine even with album names that have spaces in them but I haven't done extensive testing.
The second part of your question is fairly easy to solve. If you look about six or seven posts above, you'll note that the subalbums thingie was fixed using pathurlencode and will be releasing soon in a new zenpress version. In the meantime, just replace urlencode with pathurlencode in your zenpress files (you already know where it looks like) and it should work fine. pathurlencode is a built-in zenphoto function. You can remove it as well, but I don't know what effect that will have on every possible variation in album names.