brm-dev

I saw on their Github page that they have submitted an update: https://github.com/benhuson/list-pages-shortcode

actually, I just figured out a new way:

<?php echo $_COOKIE['ref']; ?>

Replace ref with whatever your cookie parameter is.

I used to be able to pass the cookie value into a form field by placing this inside the field value:

<?php echo $_COOKIE[get_option('cookie_param1')]; ?>

But now I can’t get that to work. Any ideas?

I use MediaTemple and have also been hacked. with ue.oeaou.com/31 in the script.

I followed the steps to remove it from the databases successfully, but what I am unsure of now is whether I am protected from future exploits. I don’t want to have to spend hours each time to repair the problem if it becomes ongoing.

Other things I have done since this hack affected all WordPress databases on my account (regardless of the WP version)…

– updated DB passwords
– changed permissions on all wp-config.php files to 600.
– changed the Secret Keys on all wp-config.php files.
– updated all the wordpress sites to WP 3.01.

I hope someone figures out how the attack happened? Whether it’s a security problem with WordPress or with MediaTemple. If it’s a MediaTemple security issue then it would seem that these precautionary measures I have taken will not stop the hack from happening again.

I was also having trouble upgrading/installing Contact Form 7 on one of my sites, because it wasn’t creating the database table for me.

Another site did successfully install so my resolution to the problem was in copying the database table from the one site to the other using PHPMyAdmin… here’s the code I used:

CREATE TABLE
wp_contact_form_7` (
  cf7_unit_id bigint(20) unsigned NOT NULL auto_increment,
  title varchar(200) NOT NULL default '',
  form text NOT NULL,
  mail text NOT NULL,
  mail_2 text NOT NULL,
  messages text NOT NULL,
  additional_settings text NOT NULL,
  PRIMARY KEY  (cf7_unit_id)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8 AUTO_INCREMENT=2 ;

Not sure if that will work as pasted above because it’s removing some of the formatting… so, here’s a link to a sql with the correctly formatted code in it, open it then run the query in MySQL or via PHPMyAdmin: https://www.weblifellc.com/images/wp_contact_form_7.sql

Here’s what worked for me, similar to what others have recommended:

add to wp-config.php:

define('WP_MEMORY_LIMIT', '64M');

I wish I knew what caused the problem initially… suddenly I couldn’t access my backend (wp-admin)… and got the error about allowed memory size exhausted… I disabled some plugins and was able to access the backend. I then renabled plugins except for any that I could live without. However, I was still seeing the message in certain places like in the Dashboard under “wordpress development blog” and “Other WordPress News”… instead of showing the feed data it was just showing the memory error within those boxes. This fix made those errors go away.

Now I just wonder if there’s a way to optimize what I am using to not go over the 32M default limit? Or is there some other error that it’s causing it to go over the 32M limit and what I’ve done is simply applying a band-aid by raising the limit to 64M?

Here’s what worked for me, similar to what others have recommended:

add to wp-config.php:

define('WP_MEMORY_LIMIT', '64M');

I wish I knew what caused the problem initially… suddenly I couldn’t access my backend (wp-admin)… and got the error about allowed memory size exhausted… I disabled some plugins and was able to access the backend. I then renabled plugins except for any that I could live without. However, I was still seeing the message in certain places like in the Dashboard under “wordpress development blog” and “Other WordPress News”… instead of showing the feed data it was just showing the memory error within those boxes. This fix made those errors go away.

Now I just wonder if there’s a way to optimize what I am using to not go over the 32M default limit? Or is there some other error that it’s causing it to go over the 32M limit and what I’ve done is simply applying a band-aid by raising the limit to 64M?

Here’s what worked for me, similar to what others have recommended:

add to wp-config.php:

define('WP_MEMORY_LIMIT', '64M');

I wish I knew what caused the problem initially… suddenly I couldn’t access my backend (wp-admin)… and got the error about allowed memory size exhausted… I disabled some plugins and was able to access the backend. I then renabled plugins except for any that I could live without. However, I was still seeing the message in certain places like in the Dashboard under “wordpress development blog” and “Other WordPress News”… instead of showing the feed data it was just showing the memory error within those boxes. This fix made those errors go away.

Now I just wonder if there’s a way to optimize what I am using to not go over the 32M default limit? Or is there some other error that it’s causing it to go over the 32M limit and what I’ve done is simply applying a band-aid by raising the limit to 64M?

Here’s what worked for me, similar to step #3 from bh_wp_fan, except with 64M (not 64MB)…

add to wp-config.php:
define('WP_MEMORY_LIMIT', '64M');

I wish I knew what caused the problem initially… suddenly I couldn’t access my backend (wp-admin)… and got the error about allowed memory size exhausted… I disabled some plugins and was able to access the backend. I then renabled plugins except for any that I could live without. However, I was still seeing the message in certain places like in the Dashboard under “wordpress development blog” and “Other WordPress News”… instead of showing the feed data it was just showing the memory error within those boxes. This fix made those errors go away.

Now I just wonder if there’s a way to optimize what I am using to not go over the 32M default limit? Or is there some other error that it’s causing it to go over the 32M limit and what I’ve done is simply applying a band-aid by raising the limit to 64M?