- This topic has 6 replies, 4 voices, and was last updated 14 years, 2 months ago by
.
-
Posts
-
If you have access to a Unix/Linux/*nix command line, change to the plugin directory and issue the following shell command:
grep add_shortcode *.php
Essentially, you are looking for all occurrences of when/where a new short code is added to WordPress.
The first argument to add_shortcodes is the shortcode string itself. The second argument is the name of the function that WordPress should call, when that shortcode is parsed.
Thanks for your reply. Yeah, I like Ubuntu Linux myself. It’s cool you’re a linux user.
Anyways, what I’m looking for is a little different, I may be wrong about the term though. I thought “hooks” referred to the following example: add_menu(‘profile.php’,…, ‘my_function’); In other words, I want to add my own functions and code when events happen, like say, when an item is put in the cart. I hope I haven’t muddied anything up. Anyways…I also had a question about how to add Google Checkout. I can do the code, but I’m not quite sure exactly where to connect it to. If you could give me some pointers that would be great. I can also share this with you guys for free, if you’d like. I’d appreciate a little props though.
. No biggie though.Thanks again.
Some of my work is in the Unix System V code… yeah, *nix runs through my blood.
“Hooks” refers to the ability to integrate your code into somebody else’s code. WordPress allows eStore and other plugins to hook into it (WordPress). eStore has the ability to hook into other “selected” plugins, and allows other “selected” plugins to hook into it (eStore). That’s what it means when you see Amin and Ivy talk about eStore integration.
The only way you are going to hook into eStore is to get down and dirty with the code, unless Amin reveals the presence of an eStore API.
On the subject of Google Checkout, please see:
https://support.tipsandtricks-hq.com/forums/topic/google-checkout-revisted#post-7904
- You must be logged in to reply to this topic.