jbuchbinder
Forum Replies Created
-
Forum: Plugins
In reply to: [Brilliant Web-to-Lead for Salesforce] Github fork with some added featuresWhy: leads are date stamped by SF – why would you need a current date field?
Someone had requested it; I hadn’t particular had an opinion on it one way or the other. 😉
Forum: Plugins
In reply to: [Brilliant Web-to-Lead for Salesforce] Github fork with some added featuresYou don’t have to have both names and values if name == value. It allows a shorthand, so instead of:
A:A|B:B|C:Cyou can instead write:
A|B|CForum: Plugins
In reply to: [Brilliant Web-to-Lead for Salesforce] Github fork with some added featuresYou’d have the same field name, you would just repeat the element with a different value. If this isn’t sufficient, open up an “issue” in the tracker on github, and someone will work on it.
Forum: Plugins
In reply to: [Brilliant Web-to-Lead for Salesforce] Github fork with some added featuresRight now, checkboxes elements are defined per value (otherwise, they would be select elements), which explains why a single checkbox element is only producing a single checkbox in the form.
Forum: Plugins
In reply to: [WP API] WP API with Advance custom fieldI patched my fork to include this capability, if you’re interested.
The commit:
https://github.com/jbuchbinder/wp-api/commit/c30a975951b85d990d6bee2d933f3fb98a9b2aad
The main repo link:
Forum: Plugins
In reply to: [WP API] Github fork with added featuresMy fork does expose a lot of that information. If it’s stored in the proper table, it’ll be exposed through the interface.
Forum: Plugins
In reply to: [Brilliant Web-to-Lead for Salesforce] Github fork with some added featuresYes, it could be done rather trivially using something like jQuery, assuming that we had a predictable id or added a class to all state selection boxes so that they could be easily selected.
To answer the earlier question, no, I’m not a Salesforce employee. I forked and started adding features because of my own needs, and it seemed to make sense to get more input from the community at large.
Forum: Plugins
In reply to: [WP API] Github fork with added featuresmyflashlab:
Honestly, I’m not sure. I’m more familiar with development on github, which is why I chose to start developing a fork there, rather than messing with the WP subversion server.
(For example, the ability to review pull requests is fantastic for maintaining software, as well as the simple branching/tagging.)
Erlend:
I’d love to try to roll the bbPress changes in — please submit a pull request for me on github when you get the chance.
Forum: Plugins
In reply to: [Brilliant Web-to-Lead for Salesforce] Github fork with some added featuresI just pushed in the change. I’d like to ask anyone who needs additional changes to submit them to the tracker on github here:
https://github.com/jbuchbinder/salesforce-wordpress-to-lead/issues
It’s easier for me to track the changes.
Forum: Plugins
In reply to: [Brilliant Web-to-Lead for Salesforce] Github fork with some added featuresNot a bad idea — I could add an “html” type to handle that.
Forum: Plugins
In reply to: [Brilliant Web-to-Lead for Salesforce] Github fork with some added featuresdrew173,
I don’t see why it wouldn’t be possible.
The format for opts is options separated by ‘|’ characters. Each of those options can also be separated into “key/value” pairs, which allow the displayed value to be different than the value which the form submits. For example:
A:1|B:2|C:3|D:would result in a select widget which displayed A, B, C, and D, but which submitted the values 1, 2, 3, and a null value, respectively. You could do a “please select a value” type of thing by simply doing something like this:
Please select a value:|Option One:1|Option 2:2|Option 3:3and setting the widget to be “required”.
Forum: Plugins
In reply to: [WP API] Github fork with added featuresIt would be done by duplicating some of the
get_postscode to be specific to the bbPress schema. I’d have to study the module code a bit to figure out how it would be done, but I’d assume that it would be moderately straight-forward if you based it off of some of the existing bits.Forum: Plugins
In reply to: [Brilliant Web-to-Lead for Salesforce] Github fork with some added featuresOkay, if it’s showing up in the source of the page, but for some reason isn’t “showing up” in salesforce, you’re configuring the name of the variable incorrectly somewhere. The plugin is properly populating the hidden field which is meant to be passed to salesforce, so it would have to be a misconfiguration outside of the scope of the plugin, IMO.
Forum: Plugins
In reply to: [Brilliant Web-to-Lead for Salesforce] Github fork with some added featuresIf you have a github account, I can give you access to the documentation wiki. You’d need to know how to write in Markdown, but otherwise it’s pretty simple.
You need to populate opts with a PHP date_format formatted field, like
Y-m-dforYYYY-MM-DDformat, etc. Otherwise it’s going to pass a null value. View the source of the page and you should see it populating a hidden variable.Forum: Plugins
In reply to: [Brilliant Web-to-Lead for Salesforce] Github fork with some added features