WPIntell

Source evidence

Memory exhausted

Twitter Mentions As Comments · support · 2013-08-28T14:26:00+00:00

complaintsentiment
highseverity
1.0relevance
2replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

3 / 22 rows with source links

13.6% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

19 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
energia99 unresolved
Hi, whenever I try to run Twitter mentions importing manually (Check for New Tweets Now) it hangs on memory exhausted. Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 85 bytes) in /home/******/public_html/wp-includes/post.php on line 606 Using version 1.5.6 of your plugin. Probably too many posts on my blog? Is there any chance to add a protection against this (sort of “pagination”, just like many plugins do when handling too much data). Any chance you can help me out? Thanks in advance, Dario http://wordpress.org/plugins/twitter-mentions-as-comments/ See: http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP And note that bumps are deleted per the forum guidelines – http://codex.wordpress.org/Forum_Welcome#No_Bumping Sorry about bumping, didn’t notice. I already edited wp-config.php of course. Not enough. Too many posts together do allocate too much memory. The plugin needs a queueing feature, some kind of pagination I think. I wish the plugin author reads this and finds it useful 😉

Comments

2 shown
WPyogi 2013-09-12T16:31:00+00:00

See: http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP And note that bumps are deleted per the forum guidelines – http://codex.wordpress.org/Forum_Welcome#No_Bumping

energia99 2013-09-12T16:35:00+00:00

Sorry about bumping, didn’t notice. I already edited wp-config.php of course. Not enough. Too many posts together do allocate too much memory. The plugin needs a queueing feature, some kind of pagination I think. I wish the plugin author reads this and finds it useful 😉