psimatrix
Forum Replies Created
-
I’ve confirmed that the hashes are the same using the above recommended method. This looks like a bug. Any suggestions on a temporary patch?
I just wanted to note that I’m experiencing the same alerts with no details. Our instillation is up to date as well. I’ve implemented the above patch to test for the hash match or not and will let you know the results.
Forum: Plugins
In reply to: [IntenseDebate Comments] get_object_vars ErrorI modified line 547 of intensedebate.php from:
if ( !is_array( $o ) ) {to:
if ( !is_array( $o ) && is_object($o) ) {This will patch the issue temporarily but isn’t a long term solution.
Forum: Plugins
In reply to: [WP Better Attachments] TIFF File Type SupportI actually tried adding the TIFF to your list of file types in the class-wp-better-attachments.php file but it didn’t work. It was easier to just write a loop to list all the files myself rather than use the plugin.
Would be nice to be able to use the plugin though so I will keep an eye out for an update.
Forum: Fixing WordPress
In reply to: hashdate script in RSS footerIf found the code block in the root /index.php file and removed it.
Forum: Fixing WordPress
In reply to: hashdate script in RSS footerI’m not finding anything suspicious in our header. Just the footer.
Forum: Fixing WordPress
In reply to: hashdate script in RSS footerI’m not able to find any code snippets out of the injection block within any of my template files or plugin files. It does appear to be the MW:ANOMALY:SP8 malware but I’m not finding anything useful online as to how to remove it.
Forum: Fixing WordPress
In reply to: hashdate script in RSS footerExample can be seen here (Caution): http://www.cagle.com/author/daryl-cagle/feed/
Forum: Hacks
In reply to: Modify custom post type after it has been registeredWas looking for a similar thing, depends on what you’re trying to modify but here’s a way to change what the post type supports.
http://codex.wordpress.org/Function_Reference/add_post_type_support
If the post type is created by a theme or plugin, it’s better to modify it after it’s registered in the event that the theme or plugin updates so that your settings will be retained.
Forum: Fixing WordPress
In reply to: Increasing Memory Limit beyond 256M@gixxer188, You are correct. I never asserted otherwise and in fact, that is the very reason why we have the server limit set higher than the WP limit as the server uses PHP for other functions other than just WordPress.
However, in this specific case, the problem was not the limit set at the server level, it was in fact the hard coded limit inside WordPress for the amount of memory that could be used by any script running inside the admin panel.
Forum: Fixing WordPress
In reply to: dynamic vertical sidebar accordion menu?From the looks of your HTML code on the homepage it appears that you are designating your CSS navigation elements with classes as “page_item” and “children”. Looking through your CSS files very quickly, I didn’t see any references to those two classes.
You may want to read the reference for wp_nav_menu as it has some examples of implementing it in the Twenty Ten default theme.
Forum: Fixing WordPress
In reply to: Increasing Memory Limit beyond 256M@gixxer188, The PHP Server limit comprises the upper limit of memory available to all PHP scripts together. As was stated in our original post, we are importing a 128MB file, which, during the import process checks for existing posts and does a lot of string parsing. This consumes a very large amount of memory when working with a file of this size and quickly exceeds the hard coded admin limit (admin_memory_limit) of 256MB.
If you want to only import one file at a time, then you would not need the PHP memory limit to exceed the limit of the admin_memory_limit. However, we are importing more than one file at a time. In this scenario, concurrent scripts running in the admin would push the limit past 256MB very quickly.
I resolved this issue because I discovered that this was reported as a bug by a Plugin developer and WordPress has acknowledged that it is a bug and will, in the future, add a configurable setting in the wp-config.php file that can modify the “admin_memory_limit”.
Additionally, we run our WordPress server on a dedicated machine with over 16GB of memory (mostly for caching). We have hundreds of authors, hundreds of thousands of posts and millions of users. When you work with a database as large as ours, WP can handle it, but often needs a few modifications.
Forum: Fixing WordPress
In reply to: Increasing Memory Limit beyond 256MWe had the Memory Limit in the php.ini set to 4096M and the Memory Limit in the WordPress config set to 1024M (as is noted in the original post). As it turns out, any scripts running under the admin have to have the memory limit defined within the /wp-admin/admin.php. By default it is set to 256M. So in fact, this is a WordPress limitation, not a server limitation.
Forum: Fixing WordPress
In reply to: Increasing Memory Limit beyond 256MIt appears that this issue was ultimately due to the fact that there is a separate memory limit for the WordPress Admin that is unaffected by the WP_MEMORY_LIMIT definition. I was able to resolve the issue by modifying line 96 of /wp-admin/admin.php as follows:
@ini_set( 'memory_limit', apply_filters( 'admin_memory_limit', '2048M' ) );Forum: Fixing WordPress
In reply to: XML import doesn’t keep authorThis issue may be moot now as it’s been so long but we had the same problem. The solution was to edit the /wp-admin/import/rss.php script at line 94 with the Id of the author from the wp_users table.
Example:
$post_author = 94;