Hi all,

theboy

New member
Apr 26, 2019
27
8
3
I am very glad to be here and it has been a while since i joined. I used to check this forum daily and has become my second home. I just wanna thank all the members and especially @babiato making this form very functional. how ever I am really searching for " if any one can make and put a course regarding how to null themes and plugins " . So if our users learn we can make this forum more productive. @NullMaster please can u do course regarding that. Once again a Huge thanks to all.
 

dannyl

Member
May 7, 2020
85
47
18
Im nowhere near as cool as @NullMaster , and they can probably do a more detailed walkthough, but in the interim:

Not sure a tutorial works, since each plugin is coded differently, but if you understand Wordpress's flavor of php, it's usually via the following (super generic steps).
  1. Spin up a new wordpress install with just the plugin / plugin family you want to null. Make sure debug_log is enabled.
  2. Open up the plugin folder in your favorite IDE (i like VScode), and search the folder for the word license. Sometimes the word is used in a file (e.g. inc/activate.php, or WordPress/Component.php ), sometimes it's in the name of the file (e.g. admin/class-bsf-license-manager.php), but they use a different word (to try to make it hard to null).
  3. Read the code. You're usually looking for a function that either checks if a license is valid ( e.g. is_license_valid() ), but it's not always that clear. Its _almost always_ going to grab the user's license from the database, so be on the lookout for get_option( 'some-plugin-license-code-field-name' ).
  4. Once you've found the validation function, try to identify the logic, as the way to null the plugin depends on this. It might be as simple as changing the function to return true;, or you might need to overwrite the variable storing get_option() (that you found in step 3).
  5. Save the file, and test! First check if the plugin now works, and then check your error_log.
    1. If the plugin now works as if its been licensed, and there's no errors in the log- congrats! Skip to step 6.
    2. If the plugin doesn't work, then you didn't null it correctly, and need to undo what you did and repeat steps 2-4. Check the error_log for hints of where you might have gone wrong.
    3. If the plugin works but there are errors in the log - then you've technically succeeded, but not very well. See if you can fix your null so it's not throwing those errors, else you'll probably have issues in the long term.
  6. Congrats! Leave yourself a note of what you did, so you can do it again next time an update is released. Bonus points if you share your code changes in the forum.
If the steps were clear but you're getting overwhelmed, google ways people have nulled specific plugins, and take a look at the functions where the null code is placed. The more you see, the easier it will be for you to identify the validation code in other plugins and the different ways to circumvent them.

GL!
 
Last edited:
  • Like
  • Wow
Reactions: p3ngu1n and theboy

theboy

New member
Apr 26, 2019
27
8
3
Im nowhere near as cool as @NullMaster , and they can probably do a more detailed walkthough, but in the interim:

Not sure a tutorial works, since each plugin is coded differently, but if you understand Wordpress's flavor of php, its usually via the following (super generic steps).
  1. Spin up a new wordpress install with just the plugin / plugin family you want to null. Make sure debug_log is enabled.
  2. Open up the plugin folder in your favorite IDE (i like VScode), and search the folder for the word `license`. Sometimes the word is used in a file (e.g. `inc/activate.php`, or `WordPress/Component.php`), sometimes it's in the name of the file (e.g. `admin/class-bsf-license-manager.php`), but they use a different word (to try to make it hard to null).
  3. Read the code. You're usually looking for a function that either checks if a license is valid ( e.g. `is_license_valid()` ), but its not always that clear. Its _almost always_ going to grab the user's license from the database, so be on the lookout for ` get_option( 'some-plugin-license-code-field-name' )`.
  4. Once you've found the validation function, try to identify the logic, as the way to null the plugin depends on this. It might be as simple as changing the function to `return true;`, or you might need to overwrite the variable storing `get_option` (that you found in step 3).
  5. Save the file, and test! First check if the plugin now works, and then check your error_log.
    1. If the plugin now works as if its been licensed, and theres no errors in the log- congrats! Skip to step 6.
    2. If the plugin doesnt work, you didnt null it correctly. Check the error_log for hints.
    3. If the plugin works _but_ there are errors in the log - then you've technically succeeded, but not very well. See if you can fix your null so its not throwing those errors, else you'll probably have issues in the long term.
  6. Congrats! Leave yourself a note of what you did, so you can do it again next time an update is released. Bonus points if you share your code changes in the forum.
If the steps were clear but you're getting overwhelmed, google ways people have nulled specific plugins, and take a look at the functions where the null code is placed. The more you see, the easier it will be for you to identify the validation code in other plugins and the different ways to circumvent them.

GL!
@dannyl. Thanks a lot for sharing. Hope most of them give a try..
 
  • Like
Reactions: dannyl

About us

  • Our community has been around for many years and pride ourselves on offering unbiased, critical discussion among people of all different backgrounds. We are working every day to make sure our community is one of the best.

Quick Navigation

User Menu