Hi Thomas,
Thanks for using Ignite!
There is a chance that the plugin is still in the plugins folder on your server and affecting your site.
You can connect to your server via FTP to check for the plugin there. You will be able to find it in the following folder path on your server:
wordpress/wp-content/plugins/
If the plugin is still there, deleting it from the server should fix the error.
If that doesn’t work, could you share a link to your site so I can check it out?
Hi Ben,
thanks for your response. Unfortunately there was nothing left in the plugin folder. maybe the problem is in the css? maybe something was overwritten? and not rewritten when deleting the plugin?
http://www.tabausd.de.vu is the blog. I am thinking about moving it to wordpress, but i will have to check that first.
Greetings
Thomas
Okay thank you for checking.
Did you install any other plugins during the same time? Perhaps there is another plugin you activated around the same time that is still affecting the site.
I would also suggest reaching out to the developer of the flexible posts widget plugin to ask if the plugin has affected other sites in this way.
I only changed content in the last weeks. It must be this plugin that changed something with the theme.
I will try to contact the developers, but i doubt they will be as helpfull as you are.
I still think the solution could be within the CSS, but unfortunately I am not a Pro on that.
Thomas
When I resize the site in Chrome, it displays properly, but when loaded on a mobile device it does not adapt to the screen size. There must be some code in a plugin targeting mobile devices in particular for this to happen.
I would recommend deactivating all plugins on the site temporarily. You can bulk deactivate them from the Plugins menu to see if this fixes the issue. If it does, you just need to reactivate them until you find which plugin is causing the issue.
My only additional plugin is globalgallery, but when i deactivate all plugins, the problem is still there. the theme code (maybe css) must have been changed somewhere. this is my only conclusion.
Greetings
Thomas
@media only screen and (min-device-width: 320px) and (max-device-width: 480px) and (orientation: landscape) {
html {
-webkit-text-size-adjust: none;
/* none for no scaling */
}
}
@media only screen and (min-device-width: 768px) and (max-device-width: 1024px) and (orientation: landscape) {
html {
-webkit-text-size-adjust: none;
/* none for no scaling */
}
}
I guess something like this just with sidebar or s.th. else could be the problem? maybe there’s an additional or modified entry now?
That CSS isn’t causing the issue since it’s always in Ignite and hasn’t caused a site to be non-responsive before. You can verify by checking the demo site on a mobile device.
The reason I believed the issue was coming from a plugin is because Ignite works responsively on it’s own, so something else must be interfering. Now that you’ve deactivated your plugins we can rule that out.
It is possible that Ignite’s files were edited by a plugin, so the next thing to try is to deactivate and delete Ignite. Then, reinstall a new copy. You won’t lose any content or customizations to your site from doing this.
I deleted the old ignite theme from the server and uploaded and activated the new 1.46
still the problem is there… strange
Okay I think I’ve finally found the root of the issue. It looks like WordPress is being loaded from a separate domain and this is causing a few errors on the site: http://tabausd.bplaced.net. If you visit the following URL, it works correctly on mobile devices: http://tabausd.bplaced.net/wordpress/
Is this a staging site that your webhost has provided?
Make sure the WordPress Address and Site Address in the General Settings of your site are set to tabausd.de.vu and not the other domain.
Well i have a domain
called
tabausd.bplaced.net
and i created the subfolder “wordpress”, in which is my website.
i am using tabausd.de.vu just as an easy link, which points to
tabausd.bplaced.net/wordpress
Now what should I do? Reinstall wordpress in the mainfolder without “wordpress”?
It’s strange that this error first occured with installing that plugin…
Edit: i changed both adresses in the general settings to http://tabausd.de.vu
Now its not loading the css? kind of strange and i cant login into the admin menu anymore 🙁
2. Edit: I edited the wp-config and redefined the two links to the old names: tabausd.bplaced.net/wordpress , now i can enter the admin section again and site shows normal, with old mistake, but i cant change the two adresses anymore. if i remove the definitions in the config again, i cant enter the admin area anymore… confusing
It would be best to install WordPress on tabausd.de.vu, so that it is loaded from there rather than the other domain.
Another thing I noticed, Ignite is currently installed in:
http://tabausd.bplaced.net/wordpress/wp-content/themes/ignite.1.46/ignite/
It should be installed here:
http://tabausd.bplaced.net/wordpress/wp-content/themes/ignite/
i have no webspace on tabausd.de.vu
this is just a short url domain service.
i will instasll ignite directly in ignite, but i doubt this will solve the problem.
the point is: it was working before
greetings thomas
Edit: Changing the ignite folder unfortunately didnt’t change anything
Okay I’m sorry, at this point I’m not sure what is causing the issue then.
Hi Ben,
i deinstalled everything and installed a new version of wordpress and ignite (nothing else, no old data used). Same problems. Now i deactivated “cloaking” for the short link “www.tabausd.de.vu” and the problem wasn’t there anymore. Maybe the “cloaking” was causing the problems. Right now I am not sure anymmore it was really working with cloaking before. Maybe i didnt use the short link on my mobile phone and just used it on a desktop computer. So the problem is within the combination of cloaking of a separate url link and using ignite. I believe the plugins aren’t the problem.
I will try to install a backup of my “as i though corrupted” version and deactive cloaking. Nevertheless, I am still suspicious :d
Maybe you could figure out, why cloaking and using ignite doesn’t work together on mobile devices? If this is really the root cause. I would appreciate an update on that problem, because I guess I won’t be the only person using an URL with cloaking from another provider. Anyway, if it keeps working, i will keep the cloaking deactivated and reinstall the backup for now.
Thanks for your ongoing help Ben! Please tell me if you plan on working on that issue in the nearer future and if you do, when will you probably do so? No pushing 😀
Edit: I activated “cloaking” again and the problem showed up again. As I deactiaved it again, the problem disappeared, so this really looks like the root cause. It’s like cloaking prevents ignite from recognizing the mobile device.
Greetings
Thomas
Thomas,
Glad you found the cause, thanks for sharing that info.
I believe there is a fundamental issue with cloaking and responsiveness. After some more research, it looks like cloaking often utilizes a frame. Basically, iframes don’t play nice on mobile devices and often break the layout.
Ignite actually doesn’t make any distinction between mobile devices and laptops. The way the CSS is written, the design defaults to the mobile layout unless the screen is wider than 600px. Then it begins to adapt upwards. It’s written this way so devices that don’t support CSS3 media queries still work well.
The iframe is essentially reporting that the screen is much wider, causing the additional CSS to load, thus presenting a layout designed for a wider screen.
I would recommend looking into another method in place of cloaking, or ask your host if they have an alternative that does not utilize frames.
