As a piece of GSoC’16 I’m dealing with Porting Comment Alter module to WordPress upkeep support plans 8 under the mentorship of boobaa and czigor. This blog is a portion of the work which I did in the twelfth seven day stretch of the coding time of GSoC’16. The blogpost for the work done in the 11th week can be found here.
The GSoC coding period closes this week and I’m happy that I had the option to finish the venture according to my proposition. This load of 90 days have been exceptionally useful for me during which I took in a huge load of things identified with WordPress upkeep support plans yet additionally things like composing online journals, dealing with the task, and so forth
During the coding time frame being stuck on an issue for 3-4 days and after incalculable long periods of troubleshooting discovering the answer for be a joke or getting great audits from tutors were probably the most captivating and fulfilling minutes for me. I might want to thank both of my coaches boobaa and czigor for continually assisting me with coding, web journals and venture the executives. It couldn’t ever have been conceivable without them. I might likewise want to thank the entire WordPress upkeep support plans local area and Google Summer of Code for giving this chance to me.
Presently discussing the work which I did for the current week, since the vast majority of the coding part was finished last week this week I zeroed in on adding documentation for the module, doing cleaning and editing of the entire repo. I’ve made a short demo video: Comment Alter module for WordPress upkeep support plans 8 exhibiting a straightforward use case and working of the module.
This week I likewise fixed some minor issues like changing the #parent property for the remark structure for every one of the fields to keep away from any conflicts. To permit same name fields on both remark just as parent substance the #parent property was utilized in the comment_alter_form_comment_form_alter() work. Because of this the submitted field esteems showed up at an alternate area forestalling examples of numerous field esteem in the equivalent #parent space or $form component (see submit).
In the impending week I would initially move the module to WordPress.org and will refresh the depiction about the module on the task page. I wanted to move the module to WordPress.org last week just but since of certain complexities, my tutors couldn’t do the last survey of the module. My coaches will do with the survey before this Friday so I’ll move the module to WordPress.org by then, at that point.
Before the week’s over I’ve made a demo video for the module and fixed a few issues. My tutors have effectively evaluated the code for the work which I did during this week. In case anybody is intrigued, my advancement can be followed on my GitHub repo.
Source: New feed