WordPress.org

Ready to get started?Download WordPress

Forums

Smooth Slider
Cannot Delete Custom Fields (18 posts)

  1. Treebeard
    Member
    Posted 3 years ago #

    I'm having trouble deleting the custom fields under every post since the upgrade to 3.0.1. Every post I create now adds 2 custom fields automatically, 'slider_style' and 'slide_redirect_url' and at the bottom, slide link URL automatically fills in. I can't delete any of them, and they are showing under the Meta information on the frontend because I need to use custom Meta fields for other things in the site.

    How do I delete those custom fields so they don't show up on the frontend? Frontend looks like:

    * slider_style: default.css
    * slide_redirect_url: http://myclientswebsite.com/the-post/

  2. Ramzii
    Member
    Posted 3 years ago #

    Im having the same problem... it doesnt help that the support of the plugin just overheated and vanished.

  3. Treebeard
    Member
    Posted 3 years ago #

    I never got an answer from them, but my client complained to them and they got a few responses (apparently trying to steal my client, I assume). Unfortunately, they never gave an answer to them either. They just said it had to do with the Meta fields (LOL! I know!!!)

    So, I ended up having to delete the meta completely from the template files, and re-type parts of the site. I don't use Smooth Slider anymore if I can help it. If a site only needs images and a single slider, I use Easing Slider - its awesome, wish they updated it for text and multiple sliders though.

  4. Treebeard
    Member
    Posted 3 years ago #

    By the way, here's the answer my client received where my template coding is blamed for the errors in the slider plugin:

    "There is some code in your active theme that pulls and prints the custom fields on your posts (single.php)

    These are the custom fields, and though they are created for each post, they should not be published. So this is not an issue with the slider, but with some extra code in single.php that prints the custom fields."

    Then I heard from Tejaswini at Internet Techies directly:

    "You can put the code in the template file not to display the custom fields specific to slider (conditional statement). You can anytime choose which meta fields to display and which to not.

    Hope you got the point, please let me know if this works for you."

    This is exactly what I've been asking for - I need to know the name of the code that is for the meta tags associated with the slider, however, I believe the plugin developer neglected to use a specific name, which is a common problem. If they don't assign a specific and unique name to their meta, it shows up on the site as code.

    The big problem, is that I am a website designer, not a PHP programmer - these are 2 different fields. For some reason, PHP programmers like to rub that in your face and not provide adequate coding, then try to blame the designers LOL!

  5. esmi
    Forum Moderator
    Posted 3 years ago #

    Why not approach this from another angle and use get_post_meta in single.php to call & display your specific custom fields instead of using get_post_custom which grabs a list of all custom fields?

  6. Treebeard
    Member
    Posted 3 years ago #

    Thank you for the suggestion. Believe me, I tried that but it didn't work. Then I searched the internet for other code but didn't find anything that worked in 3.0

    Thing is, I don't have this problem with many plugins, only this and the Favorites plugin causes an issue. So rather than waste more time, I just deleted the plugin... To fix it, I'd have to install it again in a test site and try different code in the template to troubleshoot, and I don't have time. If the developer would simply send us all a line of code so we don't have to decipher his code, that would be ideal. Since I did not create this plugin, I would expect the developer to know there's something missing in the plugin code and add it for the next release, but nothing so far.

    I'll stick with the developers that really care enough to add that code into their plugins, because so far, there is only 1 other plugin that causes this problem that I know of, and all others have never been an issue. So it's not the template, it's the plugin...

  7. esmi
    Forum Moderator
    Posted 3 years ago #

    So it's not the template, it's the plugin...

    I have to disagree. A theme should not be using get_post_custom to display all meta fields as the theme author cannot ever know what custom fields will (or won't) be used over time. Failing to do so seems plain lazy.

  8. Treebeard
    Member
    Posted 3 years ago #

    Actually I was just using the_meta - is that the wrong way to use it? Should I use something else?

    This site was done a long time ago so I can't fix it now, but if that was the wrong code to use, I'd be really happy to find out what I should have been using.

  9. esmi
    Forum Moderator
    Posted 3 years ago #

    Use get_post_meta so that you are only calling for specific custom fields.

  10. Treebeard
    Member
    Posted 3 years ago #

    I thought about doing that, but the client wanted to have the ability to create several fields. Wish there was a way to isolate the custom fields that were being displayed by the smooth slider plugin, but I never found out what they were called. Do you know? Then I could hide them instead of limiting my clients to specifically named custom fields.

  11. esmi
    Forum Moderator
    Posted 3 years ago #

    It looks like the slider fields are called slider_style and slide_redirect_url.

  12. Treebeard
    Member
    Posted 3 years ago #

    That's correct. Do you know how to hide those? I tried different code that I found on the internet, and here, but nothing worked.

  13. esmi
    Forum Moderator
    Posted 3 years ago #

    Site/post url?

  14. Treebeard
    Member
    Posted 3 years ago #

    Sorry I don't understand, are you asking for the URL to the live site I was working on when I posted this?

  15. esmi
    Forum Moderator
    Posted 3 years ago #

    Yes.

  16. Treebeard
    Member
    Posted 3 years ago #

    I would, but I don't want their website coming up in search engine results with a link here. Also, I don't see the point, you cannot access the code, and it's been deleted from the template. Why do you want to see the site, is there something you can see on the frontend that would help with the solution? Just wondering.

    Happy New Year~

  17. esmi
    Forum Moderator
    Posted 3 years ago #

    Looking for any markup hooks that could be used to hide those custom fields from the display.

  18. Treebeard
    Member
    Posted 3 years ago #

    Yea, did that already, there aren't any. That's why I ended up deleting the custom fields altogether.

    Thanks anyway though.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic