Epox

Thank you very much, this trick saved my life too with the same blank editor page problemn after 6.7 update. Nor plugin turning off or default theme helped but this line in wp-config:
define( ‘SCRIPT_DEBUG’, false);

Hey Spehen,

Thanks for your reply, and the really fast work. Your test results seems to be perfect, so it should work now. Keep up the good work!

I have the same problem with WP 4.9.6 and 2.0.2.
Unfortunatley I do not have success with editing in Databese described by @quiqueweb.

• This reply was modified 6 years, 10 months ago by Epox.

I just discovered that I can add them if the Requied switch is off when adding cookies or consents.
I will try all functionalities, ad get back if it is really a problem. Till then this problem is solved / not existed. Thank you very much.

We have the same problem… Thank you very much for the fix in ancipation.

The page throws a 404 for https://behstant.com/negocio/js/scripts.js.
Visually i can not see any labels/texts on the fields, the only visible text is Datasoft Engineering. on the head, and the security question.

I have this error message too, but the minify is working very well.

Just want to tell, that PowerTags 1.6.5 seems to work very well with NextCellent 1.9.23.
My only problem is that NextCellent have some css modifications, what is modify my custom Powertags gallery display styles too… but this is just cosmetic.

Thank you svery much! I’ll test it too and get back with the results…

Hello Sardbaba,
Found a list of NexCellent compatible NextGen 1.9.x plugins here: https://wpgetready.com/wiki/nextcellent-plugin/compatibility-list/

I just would like to suggest the NextGen Public Uploader’s discussion, what contains a NextGen plugin detection simplification for NexCellent compatibility.
Altrought I do not know if PowerTag’s will have problems with the NextGen plugin directory or not.

I wuold like to be the the second who ask you Sardbaba to modify the plugin activation process please.

Since NextGen 2.0+ is not the way tons of earlier NextGen users want to go with, our only option is to switch to NexCellent – what is based on 1.9’s codebase and fully compatible with the old architecture.

I would like to ask for your help/change in the activation checkings, cause 50% of our site is based on PowerTags, so our only way to switch to NexCellent is if you can update PowerTag’s code.

It should be enough to check for not only NextGen but for NextGen or NexCellent.

Thank you for your kind efforts in ancipation!

When will it be incuded, what is the planned release date of the next version? This is a musch have feature to let me use this plugin. Thank in ancipation!

It could be a great and easy to implement feature for us.

Hello markus74,

Did You find a solution for this problem? I have exactly the same problem. I just cleaning up my site: removed WPML string translation, uploaded some new PO files. Tuned W3TC cache plugin. Than completly removed it cause trought that may caouse the bug.

Now I have no idea, why the WooCommerce’s javascripts completly stopped working – including shipping same as billing address one.

Could you help me please?!

+1 here too!