Black Friday: Up to 40% off all plans!

Offer automatically applied at checkout
Days
Hours
Minutes
Seconds

FAQs

Find answers to common questions and step-by-step solutions.

Glossary

An alphabetical list of terms and their definitions.​

Video Library

Discover our tutorials

Why You Should Not Modify the Plugin Code Directly

Note: These documents refer to features and updates in the upcoming v5 release, which will be available soon. Some information may not apply to earlier versions. Stay tuned for the official launch announcement!

IN THIS ARTICLE
Avoid directly modifying Aggregator's code to prevent losing changes during updates and potentially voiding premium support.
Contents

Whatever change you would like to make to Aggregator or any of its premium plans, please do not modify the plugin code directly.

What we mean by this, is that if you want to make changes, customizations or any other improvement to the plugin, you need to find a way to do that without touching the plugin’s original code directly.

Why so?

Here are a few reasons.

  1. When we release an update for the plugin you modified directly, and you process that update, your changes will be lost, for good (unless you have a backup somewhere).
  2. When you modify any of the plugin code directly, we cannot know what impact that will have on the plugin or your WordPress site in general, so if any issues crop up, we cannot help you solve them.
  3. Your premium support is voided if issues occur after making direct changes to the plugin. Unless you revert to the plugin to its original state and then reproduce the issue, we can never guarantee that the change did not cause the issue, and that goes outside the scope of our support.
  4. It is bad practice. Find a better way through a new plugin just for modifications, or by asking a developer to help you out.
GIVE FEEDBACK

Was this article helpful?

Still stuck?

Find Your Perfect Plan

Answer a few questions, and we’ll recommend the best option for you!