Forum Replies Created

Viewing 15 replies - 1 through 15 (of 35 total)
  • Thread Starter halibutt

    (@halibutt)

    In case somebody stumbles on my last post, you can easily change this “Dislay” heading by including the heading="YOUR_NAME_HERE" in your [ portfolio ] code.

    Thread Starter halibutt

    (@halibutt)

    Thank you, this worked like a charm. ?? I’ll let you know once I post the Polish translation (when my site is back up and running), feel free to use it anyway you see fit.

    It seems the only hard-coded non-translatable string is the word “Display” right next to the list of features (user-side). Everything else is now in my native language. Thanks again for your help – and for this great plugin ??

    Thread Starter halibutt

    (@halibutt)

    Sadly, I don’t know where to put the load_plugin_textdomain() function, so whether it’s arconix-portfolio, acp or anything else in the .po and .mo files doesn’t change much, does it. I tried to put the entire clause in plugin.php by trial and error, but nothing seemed to work.

    Also, are you planning to release this new localizable version any time soon? It seems to me it’s already localization-ready, all text clauses are properly marked (or are they?). The only thing it’s lacking is the load_plugin_textdomain() thingie to make it work for all of us out there.

    The reason I’m asking is that I’m working on my new page right now and I’d really like to use your plugin as it seems to be the best out there. However, it’s of no use to me if it’s in a language my users will not recognize (hence the translation I made).
    Cheers

    Thread Starter halibutt

    (@halibutt)

    Just to make it clear, adding the following code right under class Arconix_Portfolio doesn’t seem to do the job.

    /**
    	* Action: init
    	*/
    	function ap_action_init()
    	{
    		// Localization
    		load_plugin_textdomain('arconix-portfolio', false, dirname(plugin_basename(__FILE__)) . '/languages');
    	}
    Thread Starter halibutt

    (@halibutt)

    Thanks, all works fine now ?? The memory requirements are much lower for all my plugins now.

    Thread Starter halibutt

    (@halibutt)

    In case you needed it, here’s a list of currently active plugins on my site. Those three mentioned before crash wp-admin even if I disable all the rest, but I’m posting just in case.

    Akismet
    cformsII
    Exclude Pages from Navigation
    fw-post-image
    Get Recent Comments
    Google Analytics for WordPress
    Jetpack by WordPress.com
    Lightbox Plus
    Picasa Album Uploader
    PJW Query Child Of
    Wordpress Download Monitor
    WP-Cumulus
    WP-EMail
    WP-PostViews
    WP-Print
    WPML Multilingual CMS
    WPtouch
    Yet Another Related Posts Plugin

    All except for WPML are at latest versions. So is the WP itself.

    Thread Starter halibutt

    (@halibutt)

    I replied there, let’s close this one then – or continue our discussion here if you prefer, it’s all the same.

    Thread Starter halibutt

    (@halibutt)

    Thanks for responding so fast. Hopefully we’ll find some solution. Take note however, that I’m close to being code-illiterate (I do most of my coding by trial and error, so speak with capital letters to me, as we say here in Poland. ??

    Here are the cPanel error logs, YARPP enabled, trying to enable WP-PostRatings or WP-pagenavi, result the same:

    [Tue Sep 25 10:24:10 2012] [error] [client 89.68.155.227] PHP Fatal error:  Allowed memory size of 67108864 bytes exhausted (tried to allocate 523672 bytes) in /home/halibutt/public_html/wp-content/plugins/yet-another-related-posts-plugin/class-admin.php on line 57, referer: https://halibutt.pl/wp-admin/plugins.php?activate=true&plugin_status=inactive&paged=1&s=
    [Tue Sep 25 10:21:50 2012] [error] [client 46.4.78.183] PHP Fatal error:  Allowed memory size of 67108864 bytes exhausted (tried to allocate 523672 bytes) in /home/halibutt/public_html/wp-content/plugins/yet-another-related-posts-plugin/class-admin.php on line 57
    [Tue Sep 25 10:20:45 2012] [error] [client 89.68.155.227] PHP Fatal error:  Allowed memory size of 67108864 bytes exhausted (tried to allocate 523672 bytes) in /home/halibutt/public_html/wp-content/plugins/yet-another-related-posts-plugin/class-admin.php on line 57, referer: https://halibutt.pl/wp-admin/plugins.php?plugin_status=inactive

    So it refers to the following lines in the class-admin.php:

    // new in 3.3: load options page sections as metaboxes
    require_once('options-meta-boxes.php');

    67108864 bytes seems like… well… way too much. Until now I’ve been using the same combination of plugins for years now, including the two (three actually) I’m unable to turn on simultaneously right now. There must be something new.

    My (loaned) server data is (Polish captions, but you’ll get the picture):

    Serwer: Localhost via UNIX socket
    Wersja serwera: 5.1.63-cll
    Wersja protoko?u: 10
    Kodowanie napisów dla MySQL: UTF-8 Unicode (utf8)
    cpsrvd 11.32.4.15
    Wersja klienta MySQL: 4.1.22
    Rozszerzenie PHP: mysql Dokumentacja

    Thread Starter halibutt

    (@halibutt)

    Cross-posted the question at WP-PostRatings’ sub-forum here, though the matter was most likely introduced by YARPP (no recent updates to WP-PostRatings and all worked fine prior to recent YARPP’s update).

    Thread Starter halibutt

    (@halibutt)

    You guys were apparently right, from the log it seems it was the php memory limit after all. I got plenty of errors similar to the one below (for various plugins):

    [Sat Dec 11 00:43:40 2010] [error] [client XX.XXX.XX.XX] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 798980 bytes) in /home/halibutt/public_html/wp-admin/includes/admin.php on line 40, referer: https://halibutt.pl/wp-admin/edit-comments.php?comment_status=spam

    I checked and my host offers only 32M of memory, which is close to peak usage of my site (typically it’s around 29, but apparently it jumps up every now and then. Do you think enlarging it to 64M might solve the White Screen of Death problem once and for all?
    Cheers

    Thread Starter halibutt

    (@halibutt)

    Where exactly should I look in PHPMyadmin? Or is it somewhere in cPanel? Anyway, I also noticed that the same happens for WP-PostViews and WP-Print.

    Also, I actually use less plugins and less memory now than before the upgrade to 3.0.3, so I doubt memory is the true culprit here. I’m nowhere near as advanced as you guys, so I might be wrong.
    Cheers

    Shane G’s method worked for me, thanks mate!
    Cheers

    Same error here (I might have forgotten to deactivate all plugins prior to the update, which most likely is the reason why all has gone wrong). Indeed deleting cache plugin files from the server fixed the issue. Thanks.

    I guess a handy alternative for W3 Total Cache would be to simply disable minify content for specific user agents (like all the iPhone-related, google them up).

    Any success?

Viewing 15 replies - 1 through 15 (of 35 total)