Testers for a new version of PN random block needed
|
joerg
Joined: 2002-10-12
Posts: 77 |
Posted: Wed, 2004-02-04 19:43
|
|
I need some testers for a new version of the random block for PN which is intended to bring better performance for large galleries (hopefully It would be nice if someone with a big gallery plays around with it for a while and tells me if it brings a boost and if the out of memory problem with large galleries is gone. Please mail me to receive a copy. Thanks |
|
). I replaced block-random.cache-file with a mysql-table. I also added multi language support (PN-style) and even better integration to postnuke by using more of the pnAPI and using the recent block-layout .
Posts: 2
Would love to test this for you (my gallery has about 60 albums and a few thousand pictures).
Posts: 56
Ok i'd like to test it on http://www.boidi.it/env i'll send you an E-Mail.
Thanks
Posts: 77
@Skin: Maybe you can do the italian translation :P
Joerg
Posts: 25
I'm trying to add the Random block to a none nuke site... not having much luck... so I'm happy to try your version since I have 1200 pictures.
Crop me a line if I'm suitable.
Regards
Kevin
Posts: 77
@KGJohnson: I think there was another topic on this board regarding a stand alone version of the block with database support. Please try the solution supposed there first.
Joerg
Posts: 30
I get this error, when after loading the block I try and click on the New Blocks link.
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 128 bytes) in /home/virtual/site69/fst/var/www/html/includes/pnAPI.php on line 515
Any suggestions
Posts: 77
At the moment I have no idea to solve the memory issues. An attempt was to use the database table instead of reading a textfile (blockrandom.cache) in memory but that did not do the trick solving the memory leak on some installations. The most people who are dealing with this problem have PN running with a lot of extensions. With every extension there is more php-code included to display the page. Cause I'm using the Gallery API in my block, I have to include much of the Gallery code. In sum, I think, that is causing the leak. To solve this there are different approaches one way is to get rid of some of the PN extensions, another not using Gallery API in the Block (not nice), the best adding some more memory in php.ini (I know, that's not possible for everybody. But remember, you get what you pay for. That's even true for webspace. Low rates, low features. :wink: ). Don't treat me wrong for that comment! 8)
Is there anyone with another ideas? If there is anyone who could tell me how to save memory I'm pleased to use that knowledge in my block.
Jörg
Posts: 30
Thanks Jorg, that is a very clear answer.
I will have a look at what apps are firing up under PN and then maybe look at the php.ini file.
Cheers
Posts: 44
Been working with the latest versions of everything lately...
Latest version of Gallery (1.4.3b151)
Latest version of random block (0.55)
The latest version of Random block does not work straight out of the box for 1.4.3.
A single line just needs to be add to the random.php file for it to work(thanks to Beckett for pointing me in the right direction on this one..)
At the top of the random.php file there are some defines...
$GALLERY_MODULENAME = "gallery"; //Change this to your module name
$GALLERY_BASEDIR = "modules/$GALLERY_MODULENAME/";
$GALLERY_EMBEDDED_INSIDE = "postnuke";
$GALLERY_NO_SESSIONS = true;
/* ADD THE NEXT LINE */
$GALLERY_EMBEDDED_INSIDE_TYPE = "postnuke";
---- end of add
Evidently the case statement that defines alot of things for user access keys off of the $GALLERY_EMBEDDED_INSIDE_TYPE variable. Which wasn't getting set.
Hope this helps out any that are having problems with the new RC that just came out...
Posts: 19
Gallery is great! Would be a MONSTER if the random block module could be used multiple times on the same page. Talking about Mambo integration here. Works great once!
Posts: 13
joerg,
I am testing PN 760 RC# you can email the random block code to be at
I will give it at try.
Jerry Jansen
Posts: 31
as of this moment, the .6xalpha (and all previous) version of the block does not seem to work with PN .76rc4
If I read something in the forums right, (I can barely speak english/spanish, much less german) he said it had something to do with changes in pnAPI, but in the PN forums I seem to recall markwest swearing up and down that any module that functioned with .75 would function with .76 - that there was no api changes..
I guess what goes for the modules doesn't necessarily go for the blocks? but how can that be? guess I'll post similar question in the PN forums..
Posts: 114
Is this working yet for PN 760?
Posts: 27
I have written my own random-block now. Its based on MySQL and its a lot faster then the orginal one. It does not require the memory eating generation (88MB) of that cache file. This also allows to get multiple random images fast or the newest images. You can see it at www.modelgraphy.com. Unfortunately, its bound into our system and I am not sure, if I rewrite it for normal g1 usage.
Well I didn't block duplicates (yet), which would be easy, but I don't care about 2 equal thumbnails on a page displaying 50 or so.
Rowald
Posts: 18
You did it very nicely Rowald, please try and see if you can share it, would really love to use it too :D
Wanna see thanks lee! It was really helpfull!
Posts: 8
I also wrote my one random-block and its also based on MYSQL, i you need it, plz pm me.