Starejosel

I found the file that was hacked by the base64 encoded file. It was the
header.php file in my active theme. It was easy to remove the inserted bit of code, as it was set off in comments:<!--start-add-div-content-->... <!--end-add-div-content-->

I hope that this info is useful.

I found a base64 encode file in my wp-admin/images file which is
called archive-dispassionate-intrigue.php
Is this likely to be the culprit? Can I just remove it?

Also, how can I safely view it without executing it?

Thanks!

Martin

I seem to have been a victim of the malware, albeit in a very strange way–I am the admin on a forum hosted at GoDaddy; the site seems to work perfectly normally. However, when I link to it in Google+ or Facebook, the preview shows the “Mayan Viagra spam”. Poking around the site [ Link removed ] (you can see it here) with firebug, I found that <p class=”nemonn”> with all the junk has been inserted on every page; however, it doesn’t show on the page.

I am not really qualified to deal with this–so any advice for a complete newbie would be appreciated. I am running WP 3.4.2, BBpress 2.2.2, and using the latest version of the Graphene theme. I have a number of plugins installed–if it is helpful, I can list them.

Any help will be much appreciated.

Thanks,
Martin

p.s. A bit of extra information which may or may not be useful: If I select and copy the whole page into apple’s textedit app, then the spam is visible at the top of the page.

I turns out that just putting in the embed code works perfectly!

Thanks for a great plugin.

Martin

Thank you–does your plugin work with lightbox? is the width of the marker
windows fixed, or can it be made larger?

Thanks again!
Martin

p.s. I really appreciate that you take the time to give support–many authors don’t.

Thank you, that is very helpful. I see that many of the capabilities of the roles have
changed, and the number has decreased drastically.

Martin

Thank you, that is very helpful.

Martin

Nope–still curious.

I have been trying some more; here is the latest status:
(I am presenting it as code to avoid problems with html that is in
the message):

the problem is to swap the default behavior and?
make return give a br tag and?shift return give a p tag.??
The TinyMCE wiki https://www.tinymce.com/wiki.php/Configuration
seems to say that is the way to do it is by setting?
forced_root_block to false.

However, when I tried that using?the
Advanced TinyMCE Configuration plugin by Andrew Ozz?,
I found:

If I use it to set?
forced_root_block to false,?
nothing?changes.?

If I set?forced_root_block?to true, which I expected
to do nothing, it breaks the editor:?
The buttons don't work, and?anything that I type
into the Visual editor?
gets wiped out when I switch to html.

If I set?forced_root_block to just a space,
when I typed in?

test
test
test
test

test
test

?it produces the following html:

< >< >test
<!-- -->
<div>test</div>
<div>test</div>
<div>test</div>
<div></div>
<div>test</div>
<div>test</div>
<div></div>

which displays as?

< >< >test

test
test
test
test
test

after submitting.

Finally, if I set?forced_root_block to div,
when I typed in?

test
test
test
test

test
test

it produces

<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
<div></div>
<div>test</div>
<div>test</div>
<div></div>

which displays as?

test
test
test
test
test
test

and there seems to be no way to produce a break.

I hope that this data is useful.

Any help would be greatly appreciated.

The solution still doesn’t look great. I’ll leave it open and hope for some new idea. Thanks for all your time and effort.

Can I select a p tag that contains a br tag?

Thanks again!

Martin

OK, thanks–actually, I do have some hope of doing better using
br~p to look for p’s that follow a br–would that work?
Can I do a series of redefinitions with increasingly restrictive selectors? In which order should I put them?

Thanks again!
Martin

OK, thanks–I think that I can figure out some sort of a compromise so that I shrink the paragraph space a bit to make the double space stuff look OK but not so much that the other stuff looks bad. I’ll fiddle.

Thanks a lot. I guess though this doesn’t really solve the original problem of changing TinyMCE’s behavior.

Should I mark this as resolved?

You probably can’t prevent that… well, stripping those tags will open a whole new set of problems.

I don’t want to strip them, I just want to restrict the redefintion of < p > to topics that do not contain < br >’s.

That is just what you will have to accept if you are going to allow willie-nillie data.

Have you ever tried to tell a bunch of poets what to do ?? ?

But I think that if I can add the two conditions above, I should be good.

Thanks again!

Martin