stevarino

I see your point now, thanks for the insight.
You’re right, it was a mistake to do this without any thought towards these issues. However I seriously don’t see a problem. We have a complete list of changes. Someone make a plug-in (maybe even an include or good ‘ol inline code) that does translations. Eventually word will get around that the plug-in is needed for backwards support. Who knows, it might even make it to the developers end of the code… In the end everything will work out I think.
Maybe the developers are aiming for leaner code and cleaner namespaces. Maybe they saw this as a community problem to solve (plug-ins are a community feature). But I honestly believe that this won’t be anything to worry with. Worst case scenario is people will simply say “older plug-ins/hacks require So-and-So’s plug-in.” A little frustration for those not in the loop but things will work out.
As a side note, maybe WP 1.3+ could have a warning label for older plug-ins. “Danger: This plugi-in has not been tested with the current WP system. Use at your own risk.” ??

I’m sorry if I’m messing something, but what’s to stop someone to make a hack which simply does something like this:
$GLOBALS['tableposts'] = $wpdb->posts; [etc...]
That way anybody still running a WP less than version 1.3 can use 1.3 hacks. So I don’t see a big problem for the end user.
As far as source-management on the development end… oy vey!

I wouldn’t even worry about a print page. Just do what the boss says: https://www.alistapart.com/articles/goingtoprint/

D’oh, thats me up there… wrong login name.

https://www.w3schools.com/css/css_reference.asp

The database is the “file” MySQL uses to store your data. WordPress needs the information specific to your MySQL. I would recommend asking your hosting provider for that info. ??

You’ll have to be sure that you’re typing proper xhtml otherwise WP might try to “correct” the problem for you…
https://www.alistapart.com/articles/flashsatay/ is the perfect article for this. ??

I honestly thought this sounded really cool last night and developed a hack for it. The problem however is that several WP functions don’t like these sorts of things – specifically wpautop and balancetags.
And I just realized the solution. ?? I’ll look at it again when I get home.

Where is the word coming from? Is it just typed into something.php or is it coming from an external source like a database?

Would this still be viewable in the archives? or are we talking about totally removing it from the database? Either way this sounds like a doable hack

https://www.shauninman.com/mentary/past/ifr_an_fir_alternative.php
Update: https://www.shauninman.com/mentary/past/ifr_revisited_and_revised.php
A really cool new way to replace text. Check it out! It uses javascript and SWF files, no PHP whatsoever. This is the stuff that makes me giddy. ??

From what I grasp of your post, YES IT CAN!
https://us3.php.net/str_replace
However there is no *direct* way to do this. If you’re using WP and want to change words in your posts that would be childsplay. If you’re talking about a regular HTML file, we might have to play some tricks such as buffers or heredoc statements.
A few more details would help solve this problem

Hmm… all things considered, the only invalid code I could find was using name instead of id to define page anchors.
As far as knowing entities, I prefer to use the w3schools’ entity guide. It has a few newer entities as well as a better organiztion and explanation for each. And 2fargon: do you know how much fun it is knowing what ö is? (yes I will admit it, I just think that character looks cool…) ??

flakkito: that w3 site is hilarious. Never saw that before and am curious why the W3 keep it up.

Awesome. Can’t wait to try it out! Thanks Markku!!!