aequalsb

@ahcreative Thanks!

my contributions:
1. you need to reload whatever screen you’re working on before attempting to upload files (ie: media screen, edit page screen, etc)

2. you can fit the solution in a one-liner:

add_filter( ‘wp_image_editors’, function() { return array( ‘WP_Image_Editor_GD’ ); } );

thanks again 🙂

• This reply was modified 6 years ago by aequalsb.

@gamesaga @pouipouidesign
if something is working as intended within it’s bounds, how can you call it broken? and how can you call it broken if you throw circumstances at it when it wasn’t designed to react to those circumstances?

FIRST, how can anyone possibly believe this plugin is actually for authentic age verification? it’s not — it was not intended to be. it is a “responsible behavior and liability cushion”. in other words, it relies on someone telling the truth to work.

if the content on a site is for 18+ and there is nothing in place to ask a visitor’s age before proceeding, then the site provider MAY be liable in some situations (note: i can’t imagine any such situations myself). also, it may be important that the provider is seen as acting responsibly.

a great example of this is “e-cigarettes”. nicotine products of any kind cannot be sold to minors — even e-cigarettes — and that industry is under extreme legislative scrutiny right now. so, adding an age-verification screen is a good way to show scrutinizers that the industry is doing all they can to act responsibly.

if there is an age checking process, and the visitor lies about their age to gain access, then it is fraudulent on the visitor’s part — thereby relieving liability from the provider.

if said site proceeded to sell a product that was illegal to someone under 18 without a more strict age-verification process, that’s an entirely different ball game. by the way, the minimum age for having a credit card is 18.

SECOND, if i visited a site that required me to be of a certain age, and i was indeed that age or older, but when i entered my age and made a typo as i was doing it, i would be quite upset to get locked out of a site. in fact, i have done that before, but the site blocked me only to notify me that i entered an impermissible age and allowed me to correct it.

if visitors are not allowed to correct typos while filling out a form, and get illegitimately locked out of a site as a result, i’d expect a lot of upset visitors — or at least, ones prone to typos.

if a site needs to be very strict about the ages of it’s visitors, then it will need to implement a much more advanced process than this plugin.

@units

is the installation in question a raw, “straight-from-the-box” installation? if it is a 100% completely unmodified WP install, then you have a real mystery. otherwise, if you have made ANY modifications, you might want to systematically check each and every modification.

a javascript added by you or a plugin that uses javascript can break the visual editor’s javascripts (or any other javascript for that matter).

try a brand new, “unshared” database with a fresh and 100% clean install of WP (to eliminate as many loose ends as possible). if the RTE works, you know that your installs have been altered in some way to break the editor. i can assert that the visual editor from versions 2.0/2.1/2.2 work fine with several types of installs for various clients — even with heavy customizations and/or plugin addons (some requiring workarounds as noted in my post above).

the OS and PHP versions you provided are not relevant information in this situation, as javascript for the RTE is handled by the browser on the client-side. of course, the content is put together on the server-side, so badly formed content may break the javascript when it gets to the client-side.

remember, and i assert this for anyone’s sake, there are only two places to look to find the solution.
[1] the browser itself
…is it a javascript-capable browser and is javascript enabled?

[2] the code
…any added content or plugins can indirectly or directly break the javascript necessary for the RTE to work — although you can almost count on the fact that any modifications that do break the RTE’s javascript will themselves use javascript.

answer this question: “what content or plugin have i added that uses javascript?” from the lineup that results from answering that question, you will likely find the culprit. note: ANY plugin should be a suspect in your lineup — it’s possible some plugins use javascript even if you think they don’t.

hope this helps…