Forum Replies Created

Viewing 14 replies - 1 through 14 (of 14 total)
  • Thread Starter ChemicalSailor

    (@chemicalsailor)

    Hi, thanks for implementing. I’ve tested the new version and it seems to work well.

    Thread Starter ChemicalSailor

    (@chemicalsailor)

    Ok, thanks for considering it.

    Thread Starter ChemicalSailor

    (@chemicalsailor)

    True, but I think being redirected to a page you weren’t expecting is a lot more of a problem than not being able to move a metabox around. Could be more of an issue if the user has already started entering post content, then changes format, gets redirected and loses unsaved changes (I take it that autosave doesn’t work without JS too).

    If the assumption is going to be that JS needs to be working to use post formats UI, then the UI should either not use anchor tags, or have them point to an in page reference ie #format-gallery.

    Thread Starter ChemicalSailor

    (@chemicalsailor)

    Yep, only occurs with JS disabled. Not an issue when JS is working because links are not followed. I only noticed the bug though because I had a JS error (something to do with my install), but could cause some unexpected behaviour.

    Basic issue: post format links should be ?post_type=custom&format=value but is just ?format=value

    Thread Starter ChemicalSailor

    (@chemicalsailor)

    Also occurs under post.php, but sends you back to edit.php instead. Same cause.

    Hey,

    Posts in the last few days got me thinking. The plugin still doesn’t work for me, but I think I may know what the issue is.

    For some reason my host doesn’t allow the server to make http requests to itself, i.e using open, cURL, wget. I figured this out when troubleshooting wp-cron.

    I doubt there is much the plugin author can do about this, it’s not really a plugin issue, but I write this in the hope it helps someone else with the same problem. Now I just have to work out a workaround. Any advice anyone?

    Hi,

    I’ve checked the call_API function in the plugin and cross checked the URL it generates. It all works fine for me when I copy it into my browser, I get a serialised array returned.
    Did this by emailing the generated url out from the plugin.

    So call_API is working correctly, and my piwik installation is working correctly as it returns the string.

    I checked get_remote_file function and that is where an empty result is being returned causing the error. I’m not sure why this is though. I see that the function should always return an array, even if it contains an error message, but it’s not returning anything? Both cURL and fopen is enabled on the server.

    I’ve tested the fopen method on my local machine and the server. It works fine on my local machine, but I get nothing returned when testing on the server, so my problem is potentially a server issue, but then the plugin tries cURL first. I don’t know if the same issue could affect cURL?

    As I said before, my piwik installation is on a subdomain. I don’t know why this should make any difference though if the API is accessed using http

    The mystery continues…

    Hey,

    Yeah I read those threads before. I’ve already tired deactivating all my plugins and it doesn’t make a difference.

    I’ve double checked that demo url. There is a slight problem with it. If you make the request without the HTML format specified all the values are returned as expected, just in an XML format, not a table. On my own installation of Piwik the url is case sensitive, it works fine specifying format=html rather than format=Html

    Just updated to wp-piwik 0.8.7

    Hi,

    Thanks for response.

    I’m using Piwik 1.4. Brand new installation.

    Using WP 3.1.3, which has been incrementally updated since 2.8.

    The settings are correct. I’ve tried prefixing https:// on the url and leaving it off.

    Opening the url in your post gives me a table with value = 1

    As I mentioned before, Piwik is accessed on a subdomain, and wordpress accessed through natural directory structure, i.e.

    analytics.mydomain.com
    mydomain.com/wordpress

    I was mistaken in my first post. I checked the database again and the plugin is saving the API token, but still not connecting to piwik installation.

    Hey,

    Got same/similar problem. Got a new install of piwik on a subdomain and set up a ‘wp-piwik’ separate user with view access in piwik. Tried putting in the API token in widget and keep getting same error as above. The auth token isn’t changing. From what I can see the token isn’t getting saved to the database in the options array. However it does stay populated in the form when I navigate away and back to the page (i.e. the value attribute is set). I don’t understand how this works if it’s not set in the database?

    I’ve tried using different tokens for different users too, none of them work.

    Hey,

    Glad to hear someone is doing this. Been searching for a email newsletter plugin powered by custom post types for a while. Any timeframe for release yet?

    Thread Starter ChemicalSailor

    (@chemicalsailor)

    Hey ArtyShow

    Thanks for the reply. I understand about multipart emails. Unfortunately my users don’t. I know you can select a preference in mail clients whether to show html or plain text emails, but again my users don’t. I’m thinking that from an ease of use perspective it’d be easier for them to set that preference in there WordPress profile. Certainly a lot easier to educate users that way.

    As you guessed I’ve got as far as setting up the options form and retrieving said options. The problem I have is in mapping that option to the email being sent. As far as I can tell the plugin hooks into PHPMailer, which is only passed $to, $message, $headers and $attachments from wp_mail(). To make the plain text preference work, I need to identify the $to variable and match that to the user profile, but at the moment I can’t get the content of the $to field.

    I think the $to variable in the PHPMailer class is private, so can’t be accessed there. I had a go at filtering wp_mail but didn’t get very far. What would be really nice is if the plugin could take the userid of recipient as an input, but that would require re-writing the wp_mail function, so again I don’t think really feasible. Right now I’m just looking for some other ideas to try, as you obviously know the plugin inside out you’re probably my best bet.

    I already patched the php for the string replacement. I also added a string replacement for %subject% in the wpbe_send_html function, as I wanted to include the email subject in the email body. I would link to the patched file for you, but can’t access my server at the moment! I’d also suggest creating a new filter in the string replacement function, so users can define their own replacements.

    Thanks again for your help.

    Thread Starter ChemicalSailor

    (@chemicalsailor)

    Also, %blog_url% string replacement, doesn’t work for me. I have my wordpress install in a sub directory to the www root and %blog_url% is pointing to the wordpress url, not the site url, as set in general options.

    Make sense?

Viewing 14 replies - 1 through 14 (of 14 total)