Hi Boldlygo,
It looks like you are using a plugin to generate your mobile site. I’d suggest looking through the settings and documentation for this plugin and you should find your answers. Sorry I can’t help more as I don’t know what the plugin is.
Also just a note, twentyfourteen is responsive meaning that it’ll work across phones/tablets etc without needing a mobile site plugin. Maybe disable the mobile plugin and see how the site looks.
Hi Joel,
I deactivated all of the plugins but I still seem to be having the same problem. Is this something I’m supposed to be able to set through twentyfourteen’s UI?
Thanks,
Hi Boldlygo,
After a bit more digging it looks like the mobile site is from Weebly. Have you used Weebly before?
I think there might be code in the .htaccess file that’s replacing your site on mobile.
Open up your .htaccess file and replace it with the default: http://codex.wordpress.org/htaccess#Basic_WP
Yes. I had a previous theme on there where I was playing around with Weebly.
I went into the root directory(wp-admin and wp-content were folders in this directory) and replaced .htaaccess with the Basic WP code. Nothing seems to have changed though. Is there more than one .htaaccess file?
I noticed that I have a folder called mobile that has one file in it called index.html. Do you think it would be okay to delete that file?
Edit for Update: I went ahead and copied the index.html in the mobile folder and then deleted it. It doesn’t seem to have changed anything…
I’m stumped. Only the root .htaccess file would be the cause.
Maybe this other support thread might help you identify something else amiss with the files: http://wordpress.org/support/topic/home-page-404-only-on-mobile-devices?replies=4
If I deleted everything in there, reinstalled wordpress, and uploaded everything in the twenty fourteen folder would that fix it? What’s the safest way to do that?
Yes that would probably do it. A better way would be to reinstall wordpress in a subfolder, copy over your wp-content folder and see if that fixes the issue (there will be none of your content in this site but don’t panic), if that does the trick than you can delete the original site and move your subfolder contents to the root. If you then change the wp-config file to match your original database details, then you should be back up and running.
Thank you Joel!
It’s using the twenty fourteen theme for the mobile view now instead of weeble. I just got one more thing to fix for the mobile view. How do i get the pages in the menu to come up when people click on the menu list button in mobile view?
Awesome, good to hear.
In terms of the broken menu now, it looks like a php error is being encountered midway through your page so all the code is not executing properly and loading the javascript needed to run the mobile menu.
In wp-config.php, set wp_debug to true:
define( 'WP_DEBUG', true );
Then it will show you where the error is occurring and you can fix it.
I can’t figure it out. Is there anyway to just turn off the menu toggle so that the expanded menu displays in mobile view?
Were you able to see an error on your page after turning wp_debug on? I’d strongly suggest fixing this issue as it’ll cause a lot of issues with other plugins etc.
If you’re able to get a error to show, reply with it and I might be able to help.
It’s not such an easy thing to change the theme to show the navigation normally no mobile screens, and won’t work very well if you add a couple more menu items in the future.
I can’t get wp_debug to work.
I figured out that if I click on ‘appearence’, ‘customize’ and then change the front page display from ‘a static page’ to ‘your latest posts’ then the menu works like it should when I’m in mobile mode.
One option here might be to the post title/date/etc and stretch the posts across the screen. Is there any downside to having the iframe in a post instead of in a page?
Thanks,
Can you expand on not being able to get wp_debug to work?
Like I’ve mentioned before, I think there is an error coming up and trying to work around it won’t really help.
Where should it show the errors?
I changed it from ‘define( ‘WP_DEBUG’, false );’ to ‘define( ‘WP_DEBUG’, true );’ by logging into my ipage account and then editing wp-config. There are three options for each file ‘edit/preview/download’. Edit and preview aren’t bringing up bug reports. Am I supposed to see the bug report from the file manager or when i’m logged into wordpress? I also tried adding ‘define(‘WP_DEBUG_LOG’, true);’ but i can’t find a bug log.
Thanks,
After you have set wp_debug to true, errors will display in place on your website. So if you visited your homepage, I’d imagine there would be an error displaying in the middle of the page, that should give you can idea of where the error is happening.
wp+debug_log will produce a debug.log file in /wp-content/ for the site.
If you can post the error here that would get us going again.
