How can I resolve license dilemma when publishing code under two licenses?

See more:

PHP

licensing

Dear Abby, her mother or whoever else is there:
A question about licenses.

I was planning on publishing some of my PHP code here. It's assorted stuff I've been working on and accumulating over several years up to the present.

I've consistently been using the GNU Affero General Public License (AGPL), for a very long time. The recommendation here is to use the Code Project Open License (CPOL) 1.02 for code published on this web site.

Currently, I have countless works spanning several years published under the AGPL, beyond my reach and control by whoever downloaded it and may still propagate it. Most of my current and future work will be based on or derived from that work.

Therein lies the dilemma. If I publish work here based on that code, but under the CPOL, it seems like it would conflict with the original work previously published under the AGPL, from which my continuing work here and elsewhere was and will necessarily be derived.

Can I take work I originally published under the AGPL and then reproduce it or derived works here, but under the CPOL instead, without triggering an international conflict that would topple governments and result in me getting my door smashed down and me being dragged away kicking and screaming into the night, never to be seen again?

I could use some sage advice during this period of grievous, soul-wrenching hell that's driving me bonkers.

Thanks.

Jay, resident of the cardboard box in the alley at the end of the street.

:)