lsaul

Hi Patrick – thanks for updating me. I’m checking back on this so I can update my review. Glad to change the review, will update as soon as I can. Really sorry about the misunderstanding.

Thanks for your understanding. I’ll have to connect with our IT team to see what might be going on with the emails possibly being filtered out.

I’ll be sure to update my review, and I apologize if it was more negative than intended. I was frustrated and working under pressure which may have inadvertently come out in what I expressed.

The plugin normally works great, there have just been a few times where it stopped. It becomes challenging when I have to work through getting it going again with other work going on. That’s all.

Thanks again.

Great, thanks! That is genuinely helpful.
It’s unfortunate that I had to leave a negative review to get such a thoughtful support response though. Which was not my intention.

I work with this plug-in on a near daily basis, and it’s used for important work. You have to understand how frustrating that is when it doesn’t work.

I was able to get the plugin to work again after restoring from backup, so there was probably an update that got through somewhere that caused publishing to fail. I still have to figure out what happened. The issue addressed does not seem to be the root cause, because publishes still work even though I’m still seeing the error FYI.

Regardless, it’s probably a good thing to correct. Glad you were able to address it.

• This reply was modified 4 months ago by lsaul.

Please don’t post information about the org in public. Especially employee names.

I didn’t post the review as the organization. For you to use the information sent privately to attack me publicly is completely unprofessional.

I created the thread with my personal account, after multiple attempts to get support via the website. Which should have the appropriate email and license info needed.

What email address does simply static support use? Neither of us have received any of those support responses and could have used that information (which I previously asked for) to find them, if we missed them.

I would kindly ask you to update your response in a more professional manner. Thank you.

Please do not mark this resolved until it is.

The fetch is running against the wrong URL throwing errors on the single page process.

In ssp-single-admin.js line 11
fetch('/wp-json/simplystatic/v1/is-running'

That URL is forbidden, and does not check the subdomain.

The URL /wp-json/simplystatic/v1/ is available and accessible.

Was there a version change that modified this code?

I’ve added the URL filter, and it’s still not respecting the config

add_filter( 'ss_origin_url', function ( $url ) {

$url = 'our-domain-url';

return $url;

} );

I’ve submitted multiple tickets, but have yet to hear back.

That’s why I posted here.

It has been 2 days.

What email address does simply static support use? So I can be sure nothing is getting filtered out.

• This reply was modified 4 months ago by lsaul. Reason: asked about email address to check

I’d also like to chime in to this request.

It would be great if you could provide options for dropdown, checkbox, radio, or tag cloud. Alternately if there was at least one example in the documentation that would be helpful as well.

The plugin works well and looks pretty good right out of the box. The purpose at least in my implementation is to add filters for multiple taxonomies on a custom post. One category only has 2 options, so it doesn’t make sense as a dropdown.

I’d be happy to do this:

Basically you should use one of the action hooks to add your own options as checkboxes (or radiobuttons) and then hide the default ones.

A little more detail would be awesome though. Thanks for the cool plugin!

• This reply was modified 6 years, 9 months ago by lsaul. Reason: Wanted to say thanks and not seem rude

I attempted to setup redirects in htaccess, but that apparently doesn’t work with WP-Engine. As of right now I’ve added redirect rules via their admin for each of the media files.

It’s not a great long-term solution as it could easily add to broken links if other team members update the site and aren’t aware of the issue.

Please let me know how I could resolve this in a more functional manner.

Thanks for providing this code. Since it is what I based the revised code on, I wanted to post the updated working version for anyone who might be looking for something like this. Here it is:

//Allows the meta-slider to be selected by adding the ID in a custom field<br />
function metaslider_insert() {
        $meta_slider_select = get_post_meta(get_the_ID(), 'meta_slider_select', 'true');
        if( !empty($meta_slider_select) ) {
            ?>
        <div id="metaslider_wrapper"><div id="metaslider"> <?php echo do_shortcode( "[metaslider id=" . $meta_slider_select . "]" ); ?> </div></div>
        <?php
        } else{
          echo "<div class=\"title\">";
         echo "<h1>" . get_the_title($ID) . "</h1>";
         echo "</div>";
        }
}
?>

That function goes in the functions.php file of whatever theme you are using. Then you just place this little snippet in your theme page wherever the slider is supposed to appear:

<?php
        metaslider_insert();
        ?>

This is based on creating a custom field called “meta_slider_select” where you would just place the ID number of the meta slider that you are using.

If you don’t want to have the else statement that displays the title, then just use this…

function metaslider_insert() {
        if( !empty($meta_slider_select) ) {
            ?>
        <div id="metaslider_wrapper"><div id="metaslider"> <?php echo do_shortcode( "[metaslider id=" . $meta_slider_select . "]" ); ?> </div></div>
        <?php
        }
?>