• Resolved Abishek Newar

    (@abishekcoolplugins)


    Hello,
    From where can i access the Source code of this project. Since, you have mentioned that it is a open-source project.
    thank you

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Val Meow

    (@valwa)

    Hey @abishekcoolplugins!

    All WordPress plugins are open source. Once you add a plugin to your server, you have access to all the code directly on your server under the /wp-content/plugins/ folder. Hope this helps!

    Thread Starter Abishek Newar

    (@abishekcoolplugins)

    Hi,

    I noticed that the plugin only includes the built frontend code. According to the WordPress plugin guidelines, the source code should be provided as well.

    Would it be possible for you to share the source code?

    Thank you!

    Plugin Author Jordy Meow

    (@tigroumeow)

    The JavaScript included with the plugin is compiled due to numerous dependencies, making it complex to build directly. If you’re interested in collaborating or contributing to our codebase, we’d be delighted to work together 🙂

    If your goal is to fork this project into something new, we can provide it as well. In that case, we’d kindly ask that your modified version remains open source and publicly accessible as well.

    However, if you’re working on a private project or a single website, we strongly recommend using the plugin as provided. The plugin is frequently updated, and manually altering JS or PHP files would prevent seamless updates. For customization, we’ve included numerous filters in both JS and PHP, specifically designed to allow developers to easily extend and adapt the functionality without altering core files directly.

    Feel free to reach out directly via https://meowapps.com/contact if you’d like to discuss further.

    Thread Starter Abishek Newar

    (@abishekcoolplugins)

    Thank you for your response,

    Actually you can just include the source files along with the package.json—there’s no need to include the full set of dependencies. Alternatively, a GitHub link in the README would also work perfectly.

    I’m not looking to contribute or fork the entire project into something new; I simply intend to extend the existing features to meet my client’s specific requirements.

    Plugin Support Val Meow

    (@valwa)

    Hey @abishekcoolplugins!

    Unfortunately, some of the dependencies we use to build the plugins aren’t available through package managers — they’re custom-made or modified versions of known libraries. So sharing package references or build parameters wouldn’t help with compiling the complete app. If you’re interested in collaborating or contributing to our codebase, we’d be delighted to work together and share the code base, of course.

    If your goal is to add specific features for your clients, the best and cleanest way to do so is by building your own AI Engine add-on. This lets you properly hook into the plugin’s tools and have your add-on show up within the AI Engine interface, making it easily accessible for your clients.

    You can follow this documentation to learn how to create an add-on: Create an Add-on

    This is exactly how AI Engine freelancers build and deliver their own custom features for clients — complete with their own admin panel, exposed settings, and use of AI Engine’s internal hooks and API endpoints.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Source Code(Open Source)’ is closed to new replies.