Second Time I update and All My Locations Disappear!
Did you report this issue? I don’t recall seeing anything in the forums or support list. What do you mean by “all my locations disappear”? On the map results or in the location manager?
There is nothing in the update routine that changes or deletes location data.
Provide some input and I can possibly fix the issue.
I haven’t reported it. I don’t know where to do this.
The database is intact and populated still, it just isn’t loaded. I’m accessing the database to list the stores on another page and my program is still working fine on that page. The last time this happened after an update the map wouldn’t “find” any of the stores until I added another location through the WP UI. They all appeared after that. This time that didn’t work.
So that’s all the info I have really. I updated to 3.7.3 (not on the review drop down list by the way), and now my locations don’t show up on the map, OR the list underneath the map, even though the database still lives on with accurate data.
To report issues click on the “support” tab on this site. It is right next to the review tab. I read & respond to posts regularly.
If you post your store locator page URL here I can possibly see what is going on from the UI.
Also, many themes and plugins do not behave. There are dozens of articles and help pages at my site (www.charlestonsw.com) discussing potential issues, misbehaving themes/plugins, and how to get around them.
Your theme is not processing AJAX requests properly. There is a bug in your theme or plugin. It appears to be the theme. This comes back from all AJAX requests which are absolutely necessary for Store Locator Plus to work.
Warning: Cannot modify header information – headers already sent by (output started at /f5/lomis/public/wp-content/themes/iribbon/core/actions/header-actions.php:448) in /f5/lomis/public/wp-content/plugins/store-locator-le/include/storelocatorplus-ajax_handler_class.php on line 164
If you use a WordPress 3.3 compliant theme Store Locator Plus will work properly. My guess is if you test with a normal WordPress 3.3 theme like Twenty Eleven all will work properly. If you are looking for well designed themes you may want to look at WooThemes. I’ve had great success & awesome support from them when something does break.
Please verify this independently if necessary. After you do so I’d appreciate it if you remove the 1-star rating as the problem is NOT in my plugin and, unfortunately, this type is one of those rare cases where I cannot come up with a creative workaround in my plugin to skirt the issue in the poorly constructed theme.
Since iRibbon is free I installed and tested on my dev box. The theme itself is OK (but does have some warnings). Thus it appears one of your plugins is intercepting the AJAX output and putting out headers incorrectly. Can you provide a list of plugins and their download links? That will allow me to hunt down the problem plugin and add it to my published “Naughty List”.
I deleted every plugin except for Jetpack & yours. Still not working. I guess it could be the theme, but why then did it work fine until I updated?
It is going to be erratic due to the headers error that is being put out. I’m not sure what is triggering it because the iRibbon theme that I downloaded today works fine.
Are you using the free version of iRibbon by CyberChimps? Do you have the latest version? Have you made any modifications?
Something in the theme is causing an HTML header to be written prematurely. When the SLP plugin goes to send the JSON (data package) header to update the map locations WordPress sends the “header already sent” warning instead.
I can disable the header in our plugin for AJAX responses, but this is NOT the correct way to handle this and may cause problems with some browsers not being able to read the map data that comes back.
BTW, I did look at the iRibbon theme and the line that is being reported as being incorrect is NOT in the current version of the theme. The iRibbon theme file that is reporting the error is 30 lines SHORTER than the line # that is generating an error. Either you are on a different/older version or your iRibbon theme files have been modified.
I test version 1.0.15 from WordPress (http://wordpress.org/extend/themes/iribbon).
I’ve been thinking about the issue and wonder if it is something specific to your location data. It is possible that the premature header is caused by an error that occurs earlier in the application.
If you are comfortable with giving admin access to your site please contact me here: http://www.charlestonsw.com/mindset/contact-us/ so we can begin a private conversation about this issue.
Someone else had a similar problem with a different plugin. CyberChimps ended up having to patch the theme & send out an update.
I have their free theme but cannot reproduce the issue after trying a number of different settings and using your location data. You may want to contact CyberChimps at the forum and point them to your site to see if they have a patch.
If I can reproduce the issue I will work on a patch, but that may require admin login access to your site.
The reason that exists is nearly HALF of all themes on the market are NOT WordPress 3.3 compliant. That means they do not properly process the WordPress footer function calls that are part of the core engine and deemed best practices for a well-designed theme. Just because a theme is “most popular” does not make it well-built. Most popular is simply a popularity contest for most downloads. “Oooohhhh that looks soooo SHINY, it must be great!” is not an indicator that something is well built.
Remember, themes have two main components. The part you look at (the UI) and the functionality (the backend). BOTH parts need to be well designed. Unfortunately many theme designers only concentrate on what you see and ignore most of the critical behind-the-scenes parts.
I went to check your site to see what issues you might be having and you are using the “advocate” theme. It has a lot of problems. Font files are missing:
- The topic ‘Second Time I update and All My Locations Disappear!’ is closed to new replies.