Forum Replies Created

Viewing 15 posts - 241 through 255 (of 263 total)
  • Author
    Posts
  • in reply to: Does web-invoice support PayPal IPN #4435

    Let’s see. You are one vote.

    If anyone else would like PayPal IPN supported in Web Invoice please shout.

    in reply to: Does web-invoice support PayPal IPN #4429

    Nope, Web Invoice doesn’t support PayPal IPN. It neither claims to be such. Web Invoice supports Moneybookers notification and AlertPay IPN.

    There is nothing preventing from adding PayPal IPN support to Web Invoice. I’ll add support for PayPal IPN if anyone is willing to sponsor development or there is a demand from the community (50 users)

    In the mean time check out Moneybookers, they are a very good alternative to PayPal.

    in reply to: (La)TeX support? #4426

    Unfortunately not. Only options would be to post as plain text. You could how ever write a (La)TeX brush for http://alexgorbatchev.com/wiki/SyntaxHighlighter.

    in reply to: front end error web_invoice_curpageurl #4423

    If you really like the plugin give it a good rating and may be post on your blog or tweet about it :)

    in reply to: front end error web_invoice_curpageurl #4417

    @billyb, thanks for reporting the issue. I have fixed it and made a release just now (should appear within 15 minutes in the plugin directory).

    The issue was introduced while localizing the plugin, my bad. Also it had missed my testing.

    Let everyone know how it goes after the upgrade. :)

    in reply to: i have not the same reslult of tou #4411

    @YannCo, I think the issue is related to your WordPress installation. None of the CSS filer or the JS files in the plugin are not accessible. e.g. http://yannco.org/wp-content/plugins/syntaxhighlighter2/files/shCore.css or http://yannco.org/wp-content/plugins/google-analytics-for-wordpress/custom_se.js (google-analytics-for-wordpress plugin).

    I think you have intentionally denying access to any file within http://yannco.org/wp-content/plugins/ .

    I suggest you http://getfirebug.com/ see what files are inaccessible via HTTP and give access to them.

    Let everyone know how it goes :)

    in reply to: Extend plugin with SyntaxHighlighter option #4408

    Just released SyntaxHighlighter2 2.0.4 with following changes:

    * Allow for options. Hide the toolbar, ruler, etc.

    * Select whether to apply the code highlighting to user comments in ‘Settings’ -> ‘SyntaxHighlighter2’

    Download the latest version from https://www.mohanjith.com/wordpress/syntaxhighlighter2.html

    in reply to: edit webform and email #4258
    in reply to: Suggestions for next version(s) of WP-invoice #4288

    @james, I just released 1.7.0 with the following changes.

    * States are no longer selectable (it’s just a text box)

    * AlertPay API bug fix

    * AlertPay IP range added (more security)

    * AlertPay country code (ISO_3166-1 alpha-3 country code) to ISO_3166-1 alpha-2 country code mapping

    * Allow just the button payments for PayPal

    * E-mail templates

    * E-mail hooks (add you own variables via another plugin)

    in reply to: edit webform and email #4252

    @senlin09, I just released 1.7.0 with the following changes.

    * States are no longer selectable (it’s just a text box)

    * AlertPay API bug fix

    * AlertPay IP range added (more security)

    * AlertPay country code (ISO_3166-1 alpha-3 country code) to ISO_3166-1 alpha-2 country code mapping

    * Allow just the button payments for PayPal

    * E-mail templates

    * E-mail hooks (add you own variables via another plugin)

    in reply to: Suggestions for next version(s) of WP-invoice #4285

    @james

    URLs will be of the format, http://www.foo.com/invoice?invoice_id={whatever} . Hash is really hard to guess (if not impossible). And a conflict in the hash is very rare (if not never).

    A definite +1 for aggregated invoices (i.e. settle multiple invoiced at once) and just the PayPal button. Come to think of it, it’s totally redundant. Of course it’s heritage from WP-Invoice.

    If anyone has a use case for PayPal form (not just the button), please put your idea in writing :)

    3 & 6 , let’s see. I’m sure you’ll love the new flow when you see it. Logging in is a big turn off for anyone. When someone is trying to pay, it shouldn’t be too hard :)

    in reply to: Suggestions for next version(s) of WP-invoice #4273

    Instead of making the client log in, allow them to provide the e-mail and the invoice ID to authenticate. I’m planning on dropping the need to create a user. Not having to create a user will definitely improve the usability/flow.

    I still think username and password is redundant when you can use a hash of the invoice id to authenticate the user. The invoice id and the has is only known by your self and the client. And invoice doesn’t have much of a life until paid.

    What do you think about that? If not (IMHO) I have to continue to have the disjointed flow of creating a user before creating an invoice.

    in reply to: Suggestions for next version(s) of WP-invoice #4267

    @james I just noticed, you had confused WP Invoice and Web Invoice. They are 2 discrete projects doing basically the same thing. But Web Invoice has more features you want :)

    in reply to: Suggestions for next version(s) of WP-invoice #4264

    @james thank you for your input. Not many will make it into the next release, but release cycles are short, so you should see most of the requested features implemented soon. See my responses bellow.

    1) Nice feature. I’ll implement it soon.

    2) I was considering tracking payments separate from the invoice. It would definitely reduce processing costs. This will definitely make into the next release.

    3) IMHO, it would be inconvenience, and doesn’t add any useful security. I would like to hear what others have to say.

    4) I’ll make it an option. As it is not critical it will not be implemented in the current release.

    5) I’m working on it, so definitely in the next release.

    6) This is not implementable unless I do 3) . Then again what’s the chance of user coming into the billing site without the invoice id. If you have come across such an instance please let me know. Also if others have any thoughts please shout.

    in reply to: edit webform and email #4246

    @senlin09, I just released 1.6.3 with the following changes.

    * Moneybookers API tested thoroughly (Thank you MB for the test account)

    * Receipt e-mail made more meaning full

    * Amount decimal points fixed (using number_format)

    * Dates and number formatting internationalized

    Hope the new release doesn’t screw up your changes (do not upgrade automatically).

    I’m working on 1.7.0, main feature addition is e-mail templates. If you have any thoughts and ideas (like extra variables that needs to accessible within the template), please share.

Viewing 15 posts - 241 through 255 (of 263 total)