Arthur Kon?ar

Hey, what’s wrong with you? The last answer to a user question was three months ago? Are you too good for support or what?

Cheers, Arthur

Hallo Leute,
wie geht’s voran? Stand der Dinge? K?nnt Ihr schon absch?tzen, wann das Tool wieder online sein wird?
Cheers, Arthur

s.u.

• This reply was modified 3 years, 1 month ago by Arthur Kon?ar. Reason: double entry

Hi,

with the exception of PHP v8.x (which my provider does not provide yet) Woo Credits works with WordPress v5.6.x
WooCommerce v4.8.x and nignx as far as I can tell. I installed it and could not find any conflicts.

Cheers, Arthur

Hi Anwar,

you do not give any hints WHY this plugin should be fake. Sorry, but your comment reads as pure spam, as if you only wanted to harm the product and its developer. Do you possibly have a similar product yourself and want to make the competition look stupid?

Please save such messages in the future, they contribute absolutely nothing to the improvement of the product. It did not help me in any way making a choice for or against Woo Credits. Please let it be. Thank you.

Regards, Arthur

• This reply was modified 3 years, 10 months ago by Arthur Kon?ar.

Quelles améliorations auriez-vous attendues ? Et pourquoi y a-t-il une si mauvaise note ?

Je pense acheter le plugin. Malheureusement, ce commentaire n’est pas un soutien pour moi ??

@simbalion : I agree with all opinions that claim that this is not a safe variant. But these people always assume that “Security through obscurity is the best solution” has to be a bulletproof security solution.

This is a childish approach. “Security through obscurity is the best solution” will certainly not be the only happy solution against hacker attacks. But as part of a comprehensive security concept (and here I include social engineering) it definitely has a raison d’être.

And IMHO @johndarrel is right: this discussion doesn’t have anything in common with the functionality of this plugin.

Ocean Extra update from v1.5.18 to v1.5.19 fixes the issue; no hassels anmore
THX to @oceanwp for the update and @veso_peso for the quick fix.

@veso_peso: quick fix works; solves the issue on all my OceanWP installations. Recommendation ’til a patch is released. THX!

Same issue here; posted the bug description as well as the message itself on OceanWP’s own support forum; unfortunately no reply so far. Still waiting and patiently enduring the error ??

@oceanwp

Confirmation: editing functions.php was the only working way to get rid of annoying sidebars.

Please read this as a feature request for a future update for OceanWP; an ‘on/off’ toggle switch switch at Customize > Blog > Single Post would do it perfectly ??

BTW, thank you for your incredible job! OceanWP fits perfectly in my every day business and at the moment I don’t ever see any reason to switch to another theme!

Keep on groovin’!

Arthur

Wohooo, sounds great! Will be updated immediately to check it out ??

Cheers!

[thumbsup] ??

Cheers, Arthur

@pritamobi

the same to me, but no answers here …

Frustrating ??

Workaround: changed to BeaverBuild

== Server Environment ==
Operating System: Linux
Software: Apache
MySQL version: MySQL Community Server (GPL) v
PHP Version: 7.2.12
PHP Max Input Vars: 1000
PHP Max Post Size: 200M
GD Installed: Yes
ZIP Installed: Yes
Write Permissions: All right
Elementor Library: Connected

== WordPress Environment ==
Version: 5.0.2
Site URL: https://www.domain.tld
Home URL: https://www.domain.tld
WP Multisite: No
Max Upload Size: 200 MB
Memory limit: 256M
Permalink Structure: /%postname%/
Language: de-DE
Timezone: Europe/Berlin
Debug Mode: Active

== Theme ==
Name: OceanWP Child
Version: 1.0
Author: Nick
Child Theme: Yes
Parent Theme Name: OceanWP
Parent Theme Version: 1.5.32
Parent Theme Author: Nick

== User ==
Role: administrator
WP Profile lang: de_DE
User Agent: Mozilla/5.0 (Windows NT 10.0; rv:64.0) Gecko/20100101 Firefox/64.0

== Active Plugins ==
Classic Editor
Version: 1.3
Author: WordPress Contributors

Duplicate Post
Version: 3.2.2
Author: Enrico Battocchi

Elementor
Version: 2.3.8
Author: Elementor.com

Email Address Encoder
Version: 1.0.12
Author: Till Krüss

Enable Media Replace
Version: 3.2.7
Author: ShortPixel

Google Pagespeed Insights
Version: 4.0.1
Author: Matt Keys

iThemes Security
Version: 7.2.0
Author: iThemes

MainWP Child
Version: 3.5.3
Author: MainWP

MainWP Child Reports
Version: 1.9.1
Author: MainWP

Ocean Extra
Version: 1.4.30
Author: OceanWP

UpdraftPlus – Backup/Restore
Version: 1.16.0
Author: UpdraftPlus.Com, DavidAnderson

WP Staging
Version: 2.4.7
Author: WP-Staging

== Must-Use Plugins ==
WP Staging Optimizer
Version: 1.1
Author: René Hermenau

== Debug ==
Errors:
SecurityError: Permission denied to access property “elementorFrontend” on cross-origin object
at https://www.domain.tld/wp-content/plugins/elementor/assets/js/editor.min.js?ver=2.3.8 – 2:0
2019-01-06 20:04 +00:00
x 4 times

SecurityError: Permission denied to access property “elementorFrontend” on cross-origin object
at https://www.domain.tld/wp-content/plugins/elementor/assets/js/editor.min.js?ver=2.2.7 – 2:0
2019-01-06 19:26 +00:00
x 8 times

SecurityError: Permission denied to access property “elementorFrontend” on cross-origin object
at https://www.domain.tld/wp-content/plugins/elementor/assets/js/editor.min.js?ver=2.3.8 – 2:0
2019-01-06 19:14 +00:00
x 3 times

SecurityError: Blocked a frame with origin “https://www.domain.tld” from accessing a cross-origin frame.
at https://www.domain.tld/wp-content/plugins/elementor/assets/js/editor.min.js?ver=2.3.8 – 2:99462
2019-01-06 18:50 +00:00
x 2 times

SecurityError: Permission denied to access property “elementorFrontend” on cross-origin object
at https://www.domain.tld/wp-content/plugins/elementor/assets/js/editor.min.js?ver=2.3.8 – 2:0
2019-01-06 18:43 +00:00
x 8 times

This system info relates to WordPress v5.0.2 + OceanWP v1.5.32 + Elementor v2.3.8. To be sure I made a completely fresh WordPress v5.0.2 setup without any themes or plugins. Then I installed only one plugin – Elementor. And guess what – neverending grey screen.

I spent hours and days of my spare time in recherche dealing with tis error. Finally a decision had to be made and so I changed the theme and the editor. I have to finish a project and my customer shurely won’t pay the time I spent to unfortunately find no solution. Bad luck.

I hope the developers will find a way to fix this problem in the future for I am definitely not alone in the dark. But for now I have to say bye bye to Elementor. It’s a shame, because I’ve seen Elementor in the past as a very promising alternative to other editors. But I just need a reliable tool, even if I have to accept other disadvantages.