401 posts Keep Walking
  • Has been a member for 3-4 years
  • Elite Author
  • Sold between 100 000 and 250 000 dollars
  • Bought between 100 and 499 items
  • Referred between 100 and 199 users
  • Exclusive Author
UXbarn says

Do you even understand your own license which you provide with the theme files? It says you can not encrypt your WordPress code because it is Open source. Encrypting the code is against WordPress license.

Whoa, take it easy man… I didn’t encrypt any of my WP codes or files. Theme package already includes every source code and it doesn’t violate the general WP license. Anyway, thanks for pointing that out. :)

@IndustrialThemes – That won’t be a problem. :)

IndustrialThemes
IndustrialThemes Recent Posts Threads Started
141 posts
  • Sold between 250 000 and 1 000 000 dollars
  • Elite Author
  • Has been a member for 5-6 years
  • Contributed a Tutorial to a Tuts+ Site
  • Referred between 10 and 49 users
  • Bought between 50 and 99 items
  • United States
+1 more
IndustrialThemes says


Do you even understand your own license which you provide with the theme files? It says you can not encrypt your WordPress code because it is Open source. Encrypting the code is against WordPress license.

Whoa, take it easy man… I didn’t encrypt any of my WP codes or files. Theme package already includes every source code and it doesn’t violate the general WP license. Anyway, thanks for pointing that out. :)

@IndustrialThemes – That won’t be a problem. :)

Awesome, thanks for taking the time to respond!

292 posts
  • Exclusive Author
  • Has been a member for 2-3 years
crossroad says

UXbarn, Sorry, I didn’t mean to sound rude. I just said in general.



Do you even understand your own license which you provide with the theme files? It says you can not encrypt your WordPress code because it is Open source. Encrypting the code is against WordPress license.

Whoa, take it easy man… I didn’t encrypt any of my WP codes or files. Theme package already includes every source code and it doesn’t violate the general WP license. Anyway, thanks for pointing that out. :)

@IndustrialThemes – That won’t be a problem. :)
3192 posts
  • Sold between 5 000 and 10 000 dollars
  • United States
  • Bought between 10 and 49 items
  • Has been a member for 4-5 years
  • Exclusive Author
organicbee says

UXbarn, Sorry, I didn’t mean to sound rude. I just said in general.


Do you even understand your own license which you provide with the theme files? It says you can not encrypt your WordPress code because it is Open source. Encrypting the code is against WordPress license.

Whoa, take it easy man… I didn’t encrypt any of my WP codes or files. Theme package already includes every source code and it doesn’t violate the general WP license. Anyway, thanks for pointing that out. :)

@IndustrialThemes – That won’t be a problem. :)

p.s using base64 to encode parts of code isnt against WordPress’s license which is GPL, Open Source is a philosophy not a license

the theme check plugin marks it for the WordPress.org site because generally base64 is used in malicious ways like embedding links in the footers etc…

3 posts
  • Has been a member for 0-1 years
lenguyenitc says

Do you even understand your own license which you provide with the theme files? It says you can not encrypt your WordPress code because it is Open source. Encrypting the code is against WordPress license.

Hi everyone,

When I used Theme-Check plugin to check my theme, it gave me many warnings of base64_encode() like following:

WARNING: Found base64_encode in the file [file name]. base64_encode() 
is not allowed.

And almost file names listed there are from OptionTree plugin that I used for creating the theme options and meta boxes. I also used base64_encode() for my purpose at some parts.

So, I’m not sure what to do to resolve these warnings about base64_encode(). Could you give me any advice?

Thank you :)

Many thanks!

by
by
by
by
by
by