southbeach030

Well my site registration is simple. Just email address and user name are required to register. Additionally, I use login-redirect to take my users to the home page. No users have rights to see the dashboard (via User Roles plugin).

Does this Register Plus plugin work on 2.0.11?

I would assume a single line of code might work for the IP address right?

Perhaps I should find the standard “user comment” email and snip the code out of there?

Any advice would be appreciated!

I solved the problem, for those interested.

I was getting this error:
PHP Fatal error: Allowed memory size of 16 bytes exhausted (tried to allocate 32 bytes) in /home/<dir>/public_html/<blog name>/wp-content/plugins/google-sitemap-generator/sitemap.php on line 1790
Allowed memory size of 16 bytes exhausted (tried to allocate 228 bytes)

I was using beta version 3.0b7 of Google Sitemaps.

I upgraded to the latest stable 3.0.3, and everything works perfectly. It builds the site map in the background, and has improved memory performance.

FYI, those should note that even though it say use on WP 2.1+, it actually works on 2.0.11

PS, Since it can take over 20 seconds to save a post, I also changed my httpd.conf file “Timeout” from 20 to 45 seconds, since it was too coincidental…

No memory issues. I tinkered around with php.ini, and it had been set to have a sufficient amount of RAM.

I thought it might have been the “max_execution_time” as it was set to 30 seconds, and a “save” post took about 20 seconds. So I raised it to 60 seconds.

I also suspect it might be the Google Sitemaps plugin..

But in regards to PHP “running out of memory,” is that specific to the “memory_limit” function? Or is that memory_limit just per process?

I had originally had it at 192M, then increased to 224M.. but thought that was way too high, and lowered it to 64M yesterday.

If I need to increase it, I can…

What is the usual culprit for the post.php box popping up?

What other server configuration settings should I be on the look out for?

Lastly, I can’t find my server logs.. any suggestions of where it’d be?

It’s now happening during off-peak times as well.

I discovered it might have been some issues with the setting in php.ini, but that didn’t help.

Any suggestions or leads?

I’ve modified some of the core files to work with some plugins… The less files I have to compare/check the better.

Ok, then Maybe I can find out what changed myself.. These security releases between 2.0.10 and 2.0.11 usually only effected a few core files, and don’t require a full-reinstall…

Can I get a list of files that had any changes between 2.0.10 and 2.0.11? I can compare those files and make the changes manually.

It’d be nice to get off RC2.. and on to final…

I tried that, and couldn’t tell what was different between RC2 and final release..

I thought these changes were documented?

anyone?

There has to be someone that can point me in the right direction.

The reason I posted here was because I’m using WordPress, and thought that someone might have gone through similar issues, etc.

Thanks

Not really mods, but more like ad codes… similar to a google ad…

in my header file, there’s a javascript call to an external ad server, and if that adserver is having issues delivering the code.. the rest of page is held up.

Is there an alternative way to iFrames that the rest of the page can load even if there’s a problem with an external code?

FYI- I remove the offending code, and the site loads fast.

Here’s an example of a slow query (25 seconds)… it seems as if it’s the “recent comments” plugin, but I cannot be 100% sure.

Can anyone suggest an index (in either wp_posts or wp_comments) that might speed up this query?

I’ve done everything possible under wordpress (caching, sql query cache, opcode cache, and more)..

# Query_time: 25 Lock_time: 0 Rows_sent: 15 Rows_examined: 72625
SELECT wp_posts.ID, post_title, post_name, post_date,
COUNT(wp_comments.comment_post_ID) AS ‘comment_total’ FROM wp_posts LEFT JOIN wp_comments ON wp_posts.ID = wp_comments.comment_post_ID WHERE comment_approved = ‘1’ AND post_date_gmt < ‘2007-07-30 13:42:54’ AND post_status = ‘publish’ AND post_password = ” GROUP BY wp_comments.comment_post_ID ORDER BY comment_total DESC LIMIT 15;

Thanks again in advance.

Here’s an example of a slow query (25 seconds)… it seems as if it’s the “recent comments” plugin, but I cannot be 100% sure.

Can anyone suggest an index (in either wp_posts or wp_comments) that might speed up this query?

I’ve done everything possible under wordpress (caching, sql query cache, opcode cache, and more)..

# Query_time: 25 Lock_time: 0 Rows_sent: 15 Rows_examined: 72625
SELECT wp_posts.ID, post_title, post_name, post_date,
COUNT(wp_comments.comment_post_ID) AS ‘comment_total’ FROM wp_posts LEFT JOIN wp_comments ON wp_posts.ID = wp_comments.comment_post_ID WHERE comment_approved = ‘1’ AND post_date_gmt < ‘2007-07-30 13:42:54’ AND post_status = ‘publish’ AND post_password = ” GROUP BY wp_comments.comment_post_ID ORDER BY comment_total DESC LIMIT 15;

Thanks again in advance.

in other words.. with the “recent comments” and “top commenters”, etc.. what kind of index should I create?

Can anyone please share a quick walk-through on how I could test this out?

Thank you!

How can I find the proper way to ensure that (at the very LEAST) I have indexes in the proper places?

myphpadmin indicates that I may not have the proper indexes, since I have a lot of full_joins taking place…

Select_full_join 295
The number of joins that do not use indexes. If this value is not 0, you should carefully check the indexes of your tables.