Forum Replies Created

Viewing 15 replies - 76 through 90 (of 102 total)
  • Plugin Author cyclonecode

    (@cyclonecode)

    Hello

    This seems very strange. I have not seen this behavior before. I will try setup a local installation and see if I can replicate this error and get back to you as soon as possible. What version of Custom PHP Settings are you using?

    Regards,
    Krister

    Plugin Author cyclonecode

    (@cyclonecode)

    Hello again Justin

    I will look into this as soon as I come home from work =) It might take a little while thought, because I will need to setup some kind of virtual environment since I am using osx.

    Plugin Author cyclonecode

    (@cyclonecode)

    Hello Justin

    Would be great if you could take a copy of your current configuration in JSON format (this can be found at the bottom of the configuration page) and email me. Also, if you are using any shortcodes with custom attributes I would need to see those as well.
    The reason that I will need this information is because I need to see how the actual feed looks and compare it with the output displayed in the block.
    Is this something that only happens on IE and Edge or is it consistent regarding browser?

    My email address is [email protected]

    Regards,
    Krister

    Plugin Author cyclonecode

    (@cyclonecode)

    You are welcome. Just think I should have named this setting display instead of view haha =)

    Krister

    Forum: Plugins
    In reply to: [Cision Block] Read more
    Plugin Author cyclonecode

    (@cyclonecode)

    Since the reason in this issue is because the feed identifier is not for a json feed I’m marking this as resolved =)

    Plugin Author cyclonecode

    (@cyclonecode)

    The issue here seemed to be that we wanted to display one block with only regulatory press releases and then another block with just non-regulatory press releases. This was at the time not support, you could either choose to display only regulatory items or all press releases. I have now added a setting called “View mode” where you can specify to display “All”, “Regulatory” or “Non-regulatory” items. This update is included in version 1.5.4 and includes a new shortcode argument view which also can be used for the same reason:

    
    view=1 // displays all items 
    view=2 // displays only regulatory items
    view=3 // displays only non-regulatory items
    
    Plugin Author cyclonecode

    (@cyclonecode)

    Hello again

    Would be great if you could send me your feed identifier so I can test this locally and figure out what is going on. Would also be great if you could copy and paste your current cision-block settings. If this works please send this information to [email protected] and I will try to fix this.

    Regards,
    Krister

    Forum: Plugins
    In reply to: [Cision Block] Read more
    Plugin Author cyclonecode

    (@cyclonecode)

    Hello again.

    The reason that this is not working is because the identifier you are using right now (296B81DF9974188B) is for an XML and not JSON feed. If you just change format to ?format=xml it will work, but the plugin only supports JSON feeds at this point, so you will need to ask Cision to supply you with a valid JSON feed identifier.

    Hope this makes sense.

    Regards,
    Krister

    Plugin Author cyclonecode

    (@cyclonecode)

    I have now looked on this and I believe this problem is because you have two shortcodes in the same page. The generated name for the cache entry is currently something like this _transient_cision_block_data_<PAGEID> so if you have two shortcodes in the same page/post then they will share the same cache entry, which of course will not work. I have created a new release 1.5.3 which should solve this as long as you specify and id for each block in the shortcode e.g:

         
    [cision-block id=first_block]
    [cision-block id=second_block regulatory=true]
    

    If this does not work try setting the cache time to 0 in order to turn it off and see if you then get a valid response.

    Regards,
    Krister

    Plugin Author cyclonecode

    (@cyclonecode)

    Hello Marcus

    Will look into this and get back as soon as possible.

    Regards,
    Krister

    Forum: Plugins
    In reply to: [Cision Block] Read more
    Plugin Author cyclonecode

    (@cyclonecode)

    Hello Filippa

    I will look into this as soon as possible and try to figure out why this is not working as expected.

    Plugin Author cyclonecode

    (@cyclonecode)

    I think I have tracked down this problem and the reason this was not working as expected was because the shortcode that was used separated each argument with a linebreak. All shortcode parameters needs to be on the same line:

    [cision-block id=swe source_uid=<FEED_UID> language=sv regulatory=true]

    The following with not work as expected:

    [cision-block 
    id=swe
    source_uid=<FEED_UID>
    language=sv
    regulatory=true
    ]

    In the above example, no parameters will be available so all default values from the cision block settings page will be used.

    • This reply was modified 5 years, 5 months ago by cyclonecode.
    Plugin Author cyclonecode

    (@cyclonecode)

    Yes the shortcode setting should override the general setting so this seems very strange? Can you please copy your current setting from the JSON field under general settings and perhaps also give me the markup for the shortcode you are currently using and send it to [email protected] and I will have a look on this as soon as possible.

    Plugin Author cyclonecode

    (@cyclonecode)

    One more question: How is your homepage configured are you using a static page?

    Plugin Author cyclonecode

    (@cyclonecode)

    Can you try to enable WP_DEBUG in you wp-config.php file and see if you receive a descriptive error message. It seems like there is some problem with the actual query string i.e ?cb_id=cision_block&cb_page=1, since this only happens when you have this in the url.

    It is very hard to say what is going on without a more descriptive error message. I have never seen this before and that is the reason why I am thinking that it has something todo with one of your installed plugins or perhaps some specific configuration with you wordpress installation.

    If you have root access to your server, perhaps you could check the web servers log files and see if they contains any more information; if you are running apache then these files will probably be located under the /var/log/apache2 directory.

    If you could give me access to either the server (best would be ssh access) or perhaps create a wordpress account I think I would be able to check why this is happening. If you create an account or give me ssh access please send login credentials to [email protected]

    Regards

Viewing 15 replies - 76 through 90 (of 102 total)