I’m building a custom search plugin for a company that has very specific needs for their searches. I’m using the search module to help me structure this project and am going to be building the form like it has.
One of the first things I’ve noticed is that they use the exp_actions table which installed modules have methods all mapped out on. In order to build my search, I need an ACT to refer to, like do_search - but since I’m developing a plugin, not a module, I’m adding nothing to represent this plugin to the database.
Would it be appropriate to add my action as a method from my php file? like ‘ACT’ =>’action’? Or is there another global method I should call instead? Would an absolute path to the plugin work? How is that generally written?
Any help appreciated. Thanks!
[removed]- thanks for your reply -
So suppose I were building a search function that needed an action in the form, to pass through the plugin to be processed - I could easily put that in the form tag, but what path would reach the plugin?
Or is what I’m doing beyond the scope of plugins entirely?
It’s not intended for a plugin, but you can build it as a module instead quite easily. You will need to have all of the files that a module requires, but it is not necessary for a module to have a control panel back end. The front end is essentially identical to a plugin. The main difference is that you will have an install routine, allowing your add-on to add itself to the exp_actions table.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.