Viewing 15 replies - 1 through 15 (of 18 total)
  • Thread Starter Noche70

    (@noche70)

    I know its the theme, but, I have an older version of this theme and its working:

    https://dev.wcfoot.com/

    Which browser are you using to see this? Have you tried viewing it in a different browser? Also when did then error first happen? One would assume after the 4.3.1 automatic update?

    Have you tried:

    • flushing any caching plugins you might be running, as well as server and/or browser caches.
    • deactivating all plugins (yes, all) to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s). If you can’t get into your admin dashboard, try resetting the plugins folder by FTP or PhpMyAdmin (read “How to deactivate all plugins when you can’t log in to wp-admin” if you need help). Sometimes, an apparently inactive plugin can still cause problems. Also remember to deactivate any plugins in the mu-plugins folder. The easiest way is to rename that folder to mu-plugins-old
    • switching to the Twenty Fifteen theme to rule out any theme-specific problems. If you can’t log in to change themes, you can remove the theme folders via FTP so the only one is twentyfifteen. That will force your site to use it.
    • manually upgrading. When all else fails, download a fresh copy of the latest.zip file (top right on this page) to your computer, and use that to copy up. You may need to delete the wp-admin and wp-includes folders on your server. Read the Manual Update directions first.

    notices the message above

    I would try contacting your theme provide. Which theme are you using of your website? If you switch to the Twenty Fifteen theme does it go away?

    Thread Starter Noche70

    (@noche70)

    Yes, if I switch to 2015 it goes away. The strange thing is that my first dev site was fine, but then when i created a copy in a different hosting and updated the theme it broke.

    Nothing is really broken but this issue is just driving me crazy!

    I am using Chrome, and the latest WP version. It’s broken in all browsers, I know its the theme, but what could I have done that I broke it? I only modified the CSSs.

    Thread Starter Noche70

    (@noche70)

    I have a fresh WP intall, I only moved the wp-content folder to wpengine.

    What theme are you using? Did you make a child theme of the theme?

    Thread Starter Noche70

    (@noche70)

    Crumina but they didn’t make a child theme, just modified it.

    Thread Starter Noche70

    (@noche70)

    The <form> tag is gone: https://screencast.com/t/3azPouDyoPz
    what could possibly do this? only CSS?

    this should look like this: https://screencast.com/t/fpkpioN5DMy

    It is your theme that is causing the problem. We have narrowed that down to that.

    Now you NEED to reinstall your theme. You must of caused some error when you were editing out the parent themes CSS. You need to reinstall the theme, create a child theme, and edit your child theme to make changes. This way you are not putting your parent theme at risk. You can read all about parent and child themes in the codex. https://codex.www.ads-software.com/Child_Themes

    Thread Starter Noche70

    (@noche70)

    Thanks!

    This is a personal question, would you suggest a child theme over modifying the parent theme? what would happen if the developer decides to upgrade the theme and breaks the child theme? would you suggest to not update the parent theme and avoid future issues?

    The importance of having a child theme is so that you can update your parent theme without losing all of your changes. Also you are not putting your parent theme at any risk. As for errors… If you only copy the files you are going to edit to your child theme (i.e. style.css, function.php, maybe header.php or footer.php, etc.) then you should not experience any issues if you update your parent theme. Just make sure that your child theme only has the files that you have edited. If you copy the whole theme to the child theme then it basically defeats the purpose of having a child theme.

    So once you create a child theme then I would update/reinstall your parent theme and then make all the changes on your child theme. Once you do this hopefully you won’t experience any errors.

    Also I believe this is talked about in the codex link that I provided.

    Thread Starter Noche70

    (@noche70)

    I understand the concept of the child-theme. My question was more like, what would happened if the developer updates the theme? It has happened to me that the developer updated the original theme, and when I updated my copy, the whole website broke.

    The developer decided to change the column names for this specific theme, and anything I hardcoded in my child-theme using the old column names didnt work anymore.

    For this reason I decided not to upgrade themes anymore, whether I created a child-theme or not.

    Thread Starter Noche70

    (@noche70)

    Also, there is the issue of discontinuing the theme, for example this one. I bought this one years ago and its long gone from ThemeForest.

    Thread Starter Noche70

    (@noche70)

    Thank you so much for your help though! ?? I appreciated.

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘The wp-admin-bar-search broke and I cant fix it!’ is closed to new replies.