normadize
Forum Replies Created
-
As I said, I’m using v1.9.5.6. If you use v2.x then you may have a different interface (v2.x doesn’t work with WP 4.5 so I can’t use it)
This is what I see in the PMPro discount code panel when adding/editing a discount code:
Forum: Plugins
In reply to: [Defa Protector Platinum] doesn't work with direct link from Vimeo Pro@jan, thanks for the comments. I thought it was the plugin author who was moderating. I had zero intentions of being rude, but wanted to point a dick move from the plugin author in order to prevent others (innocent and less savvy users) from wasting their money and time on the so called “free” fix he provides. I made it more clear in the above post.
Forum: Plugins
In reply to: [Defa Protector Platinum] doesn't work with direct link from Vimeo ProI just told you how to fix a bug in your own open source code, i.e. Vimeo does not send the same headers for HEAD as it does for GET (doesn’t respect the HTTP standard) and you need 206 for Firefox. It’s easy to fix your code with this information … you should be happy, not upset.
Your Act is against the law. I warn you this time or I will report an international police to put you in jail
The definition of open source is that anyone can download and modify the code. If you think that’s illegal then you either have serious issues, or you are too young to contribute with code on public forums. In any case, you should refrain from making public threats about putting people in jail. Nobody takes you seriously but you may get banned from these forums if someone reports you.
Lastly, yes, you did intentionally hide a flaw in your code and claim it’s all free but you are in fact turning a profit. Here’s what you say in the other thread about the error, which you clearly aware of:
If you have a Header Already Sent Error You can use our free and paid plugin to fix this . It cover all the universe. Download now at : https://www.juthawong.com/downloads/wordpress-header-already-sent-fix-plugin-for-free-and-paid/
Please don’t hating on me that I don’t give this for free on WordPress Repository and also please don’t burn my house.Instead of fixing the error in the main code, you chose to write a separate plugin and to upload the so called “free” version of it to a website that requires one to register for cash prizes in order to download (link) while the other version you are selling for a price (screenshot). It’s your code, sure, but pretending and claiming it’s free and that you don’t get financial gains is defined as “a dick move“. It violates the principle of free and open source software. But good luck to you …
Regards.
p.s. The browser will always leave the file in the cache. That’s a widely known issue. I have my own code to hide Vimeo links using a similar technique and I suffer from the same issue (encrypted HLS would make it harder) but I believe in free software and free methods of access to information. You seem to believe in what’s called “security through obscurity”, which is unhealthy. Don’t be upset.
p.p.s. Stop editing my posts!
Forum: Plugins
In reply to: [Defa Protector Platinum] doesn't work with direct link from Vimeo ProIt’s actually pretty easy to make it work with Vimeo. I looked at your code and it does a few things wrongly. Right now your code fetches then passes the wrong headers (it also makes 3 request per seek, which is overkill but can also break the flow between the servers). Use GET (not HEAD) and serve with 206 status not 200. Anyway, I’ve written my own code for this and it works just fine with Vimeo, including seeking, tested with both Firefox and Chrome. I may make a proper plugin when I have more time.
I noticed that you intentionally introduced the “headers already sent” error by putting session_start() in wp_head instead of wp_loaded, and now offer a 2nd plugin for which you ask money …
[rude comment moderated]
p.s. This kind of protection is pretty much useless. The .mp4 file can be found in the cache folder. For Firefox in Windows, that is %appdata%\local\temp\mozilla-temp-files\<some-big-file>. Just rename it to movie.mp4. This is even easier than installing DownloadHelper …
Forum: Plugins
In reply to: [Defa Protector Platinum] is there a demo?That’s quite an odd approach. I asked for a demo precisely to see whether I want to buy a server or not. I don’t have a server yet. Depending on how well/bad your software works against easy download tools, then I can save time (and possibly money) hosting my videos on a dedicated site rather than buying my own server.
Would you (or someone else) mind put a demo link here in this thread, which is not that public?
Or maybe I can email you and you can provide a demo link by email? I don’t know your email though.
p.s. if you believe in your software then you should believe in it all the way
Forum: Plugins
In reply to: [W3 Total Cache] can't get 304 to work … headers seem wrongly setA workaround for me was to force max-age=0, e.g.
Cache-Control: max-age=0, public, must-revalidate, proxy-revalidate.As a side note, W3TC also sets redundant Cache-Control and Pragma, once in the main
.htaccessand then also inwp-content/cache/page_enhanced/HOSTNAME/.htaccess.It also sets
ExpiresByType text/html A0in the main.htaccessand thenExpiresByType text/html M0inwp-content/cache/page_enhanced/HOSTNAME/.htaccess… note that the former is the one that matters.Forum: Plugins
In reply to: [Enhanced Custom Permalinks] notices and calls to deprecated functionsIn addition, when developing it’s always a good idea to set
define('WP_DEBUG', true);inwp-config.phpso that you can see the errors, otherwise WP disables error_reporting in the code, which overrides the php.ini or .htaccess settings.In any case, this is a great plugin. I hope you’ll be able to keep it updated! Thanks again for all the effort.
Forum: Plugins
In reply to: [Enhanced Custom Permalinks] Was my thread deleted?Ignore that, they reappeared (central WP forums issue perhaps).
Forum: Plugins
In reply to: [Enhanced Custom Permalinks] notices and calls to deprecated functionsSome more:
Notice: Undefined index: path in /WWWROOT/wp-content/plugins/enhanced-custom-permalinks/enh-custom-permalinks.php on line 331Notice: Undefined variable: idList in /WWWROOT/wp-content/plugins/enhanced-custom-permalinks/enh-custom-permalinks.php on line 173Notice: Trying to get property of non-object in /WWWROOT/wp-includes/post-template.php on line 29 Call Stack # Time Memory Function Location 1 0.0011 388864 {main}( ) ../plugins.php:0 2 0.5989 35537704 require_once( '/WWWROOT/wp-admin/admin-header.php' ) ../plugins.php:361 3 0.6094 35600008 do_action( ) ../admin-header.php:122 4 0.6094 35602528 call_user_func_array ( ) ../plugin.php:429 5 0.6097 35602616 custom_permalink_trigger_conflict_check( ) ../plugin.php:429 6 0.6097 35602824 get_the_ID( ) ../enh-custom-permalinks.php:504Notice: Trying to get property of non-object in /WWWROOT/wp-includes/post-template.php on line 29 Call Stack # Time Memory Function Location 1 0.0011 388864 {main}( ) ../plugins.php:0 2 0.5989 35537704 require_once( '/WWWROOT/wp-admin/admin-header.php' ) ../plugins.php:361 3 0.6094 35600008 do_action( ) ../admin-header.php:122 4 0.6094 35602528 call_user_func_array ( ) ../plugin.php:429 5 0.6097 35602616 custom_permalink_trigger_conflict_check( ) ../plugin.php:429 6 0.6098 35603200 get_the_ID( ) ../enh-custom-permalinks.php:505@mightypixel: the person behind OneAll (it’s just one person) does read and reply in these forums (*) and you can be sure he read this thread too. I’m disappointed by the lack of reaction towards such important issues …
I would go as far to say that the OneAll plugin should be banned by WP for this privacy breach given that it is not specified in the docs or at install time, nor asks for relevant permission.
I’ve stopped using OneAll and have been since recommending against it.
(*) he had some interventions in other threads (see the thread regarding the logo/brand removal) which were also disappointing.
Forum: Plugins
In reply to: [Really Simple CAPTCHA] Transparent/alpha background patch provided@fannur: the issue I posted about is how to make it transparent, not how to change the color.
Well, you have to thank the WP moderators then for their profound insight in limiting the improvement of WP plugins … the WP forums do not provide with private messaging so in this instance there is effectively no way for users to contact each other for purposes such as this.
Obviously, I’m not going to post hundreds/thousands of lines of code in the forums nor create a new plugin before it is tested by others so volunteers are needed for testing, but thanks to the WP moderators that’s now basically impossible. I’ve developed and already using it for my websites so this is affecting the others, not me.
I’m not going to post my email again.Cheers.
p.s. The thoughtful moderator might want to provide with the ToS/rules of the WP forums where it says that we are not allowed to leave our email address in any form (obfuscated or not).
That sounds great, thanks!
Forum: Plugins
In reply to: [User Role Editor] Lots of PHP noticesOk, I can confirm that after deletion of the singular caps, the notices are gone.
I’ll do more tests to make sure nothing else is affected. From what you are saying, if I don’t create singular caps (or if I delete the ones I created) WP will still generate singular caps to use internally, correct? How exactly is WP using singular caps? Are they actually needed internally?
It might actually be a good idea to detect when a user is trying to register a singular cap and provide a warning. It’s not straight forward, I know (check only the ones starting with edit_* or delete_* or read_*, coupled with matching on existing custom post types but that’s unreliable).
Many thanks for your time!
Forum: Plugins
In reply to: [User Role Editor] Lots of PHP noticesOur discussion goes to the circle. I have suggested you to check, that you see notices from WP core because of improper use of User Role Editor to create manually custom post type meta (singular) caps. If you do not wish to follow it, it is nothing I can do.
I think I went to the length of posting full call stacks of the code for you to see exactly what’s going on. I also un-asigned all singular caps (that’s what I thought you meant). I’m actually trying to follow your advice … You give lengthy replies, which are much appreciated, but have not really answered my question or if you did, it’s still confusing to me, maybe I haven’t had enough coffee or sleep. So once again:
Are you saying I should DELETE the singular caps using URE? (i.e. select the cap, click delete). A yes/no answer would be great.
The WP docs are confusing too as they suggest that singular caps should be created, but not generally granted to roles. That’s exactly what I did, i.e. created them but not granted. You seem to be saying something different, but I’m not 100% sure.
As a side note, I disagree that caps are stored in roles. The same cap, e.g. “edit_posts” can be granted to any role, and also to multiple roles simultaneously. You probably mean the granting of caps, but the cap itself is standalone.
