I noticed in 3.0 when I was on any screen that was using bt_screen.php (I'm pretty sure this is a new screen by the way), that if I clicked on the Application Home link (top left), I'd get Not Found on this server. So, I dug around and spotted what I think could be causing this. domain/BT-server/bt_v15/bt_app/bt_screen.php (singular, not screens.php) Line 35 $controlPanelURL = "../../../bt_v15/bt_app"; there are (3) ../ and should only be (2) like: $controlPanelURL = "../../bt_v15/bt_app"; Not totally sure, but it fixed the problem... Ross

Nice find! I had the same issue, but just lived with it before. Thanks for tracking it down and sharing! I just made your recommended change in about 30 seconds and it worked like a charm :)

Is this a Core thing, or a Plug In?

An example would be if you added "Menu Simple" to an app in Manage Screens and Actions... then click on it... if you now look up at the URL displayed, you'll see it uses bt_screen.php NOW, from here, if you click on "Application Home" (main nav left) you may experience what I did. Not Found. The issue will happen with any plugin that uses bt_screen.php (I think)... at least for me it did. I'd be curious if you try and it does happen, ... then I'll know it was not just some url issue on my server.

@nicksapps: it's in the core, on self hosted @rossideas: Yep, that's exactly what happened before. I specifically noticed it if I went to any of my plugins screens (the settings for that "screen" in my control panel), and then hit the "application home" link. It would always return "not found", so I just got in the habit of clicking my logo in the top left corner, which would go to my control panel home instead of the application home. But your fix made the "application home" link work the way that it's supposed to, so it's not just you. :)

Great... thanks Angry Ninja. :~)

rossideas, Nice find! Thank you. I made the repair and it works fine. Dave

Ninja- I PM'ed you earlier

Yep, I had a chance to read it. I'll have to get back to you later tonight or in the morning about it, cause I gotta check my schedule first and see what I can do. :). Shouldn't be a problem though.

I use "Menu Simple" but I don't recognize: Manage Screens and Actions. My Menu Simple functions, however, as I have posted for 2 weeks, in Android, the rows are clear with gold text, when they should be solid black with gold text. Works in iOS7. Who is going to bring this to David's attention? Self Hosted 3.0.

Nicks Apps... Manage Screens and Actions, is just where all your screens are listed for your app. "Menu Simple" is not the issue, it is just an example of a plugin that uses bt_screen.php. Once you are on your screens page, if you click on any of your screens and notice above in the url that it is using bt_screen.php...AND then click on the Application Home link on the top left... you'll probably experience the "Not Found". If you are picking a screen that goes to files/plugins/ it won't happen.

I always wondered why it did that with menu simple on my self hosted.thanks!

Are you talking about Android, or both Android and iOS 7? I can't find "bt_screen".anything in iOS Xcode. But I did in Android Eclipse. So I clicked on some of the Menu Simple files (in Eclipse), and even though I have this in my Control Panel "itemType": "BT_screen_menuListSimple", "itemNickname": "Main", "navBarTitleText": "Main", "listRowBackgroundColor": "#000000", "listTitleFontColor": "#FFFF33", "listRowSelectionStyle": "none", All of the Menu List Simple files in Eclipse were "listRowBackgroundColor": "clear". I changed them to "listRowBackgroundColor": "#000000"... but in the Simulator, and on my device, the rows are still clear, then transparent blue after selected. My Simulator is using API 19.

No, this isn't xcode or android, it's the self hosted script... the files you upload to your web host to run your self hosted BT Server. it's the files located in /BT-server on your web directory. No ideas on the menu with image android stuff... I do iOS only, so afraid I can't help with that... but thats a whole different issue, not related to rossideas fix for the issue he mentioned in this thread.