Directly editing plugin files?

Hello @thequreshi ,

Thanks for your thoughtful query.

You are right on the comment that the changes will be gone with the update. Our first priority on a modification is that you use a child theme and if there is any hook available then use that to make the modification. But sometimes due to the customer request we have to suggest them to modify a core plugin file. We always notify them the changes will be gone with the update so try to keep a backup of the modification.

We are trying to make our plugin more developer-friendly so hopefully in future you can work on the code without modifying the core files.

Regards,
Rashed

Thanks for the response, Rashed.

I see you mentioned that “sometimes due to the customer request we have to suggest them to modify a core plugin file”

Is it the right way to provide support? Certainly not. The right way is to tell them the right hook that they can use in the child themes for the customization.

The job of the support team should be to guide the customers to the right hook rather than suggesting direct edits!

Best,
Qureshi

Hello @thequreshi ,

I get your point but I have already explained why we do that and also we made sure to notify the user about the consequences. Please check this part of my reply –

if there is any hook available then use that to make the modification. But sometimes due to the customer request we have to suggest them to modify a core plugin file. We always notify them the changes will be gone with the update so try to keep a backup of the modification.

Providing the right hook and file locations are our first task whenever we are asked to providing customization guideline. I think you misunderstood my last reply. However, thanks for your input and we will try our best to implement your suggestion in our practice.

Thank you.

I understood your reply brother ??

Anyway, I have made my point. Which is that the support team should NOT suggest direct editing of the files under ANY circumstances whatsoever.