Hi All, I have moved across to self hosting and working on my first app. Searching through this forum, I have manually (FTP'd) the plugins after the Self Host server 'install' didn't work. All was looking good, the server found my new plugins and the first one I used worked a treat (BTA Design Menu). The others (standard plugins, such as HTML Doc and Custom URL) don't seem to be working. Rather than getting the expected screen to work through it settings, I'm getting a text based screen with links (looks like function headings) that don't work or provide a blank page. I suspect it's just a setting of some description, but not sure why BTA Design worked and the others aren't..... :( Any help would be appreciated. Thanks in advance.... R., Craig. P.S. - I'm using Safari (Mavericks) on a MacBook Pro, host is HostGator.

I'm just guessing, but then again, sometimes I'm a pretty good guesser ;) The BTA design menus are probably using an index.php file for the 'plugin landing page'. This is the 'config' page that you use to set values and stuff in the plugin. The 'new' style plugins don't use an index.php file… in fact, no PHP files are allowed. So what is 'supposed' to happen is If it's an 'older' style plugin, the BT system would detect the index.php page, and allow that as the 'config' page. If it's a newer style plugin, there is NO index.php, and BT uses a default landing page (bt_screen.php) and places this value into your database plugin table (in the field 'landingPage'). What I suspect is happening is that the BTA using the index.php has no problems, but while you manually 'added' the plugins, there was nothing to insert the value 'bt_screen.php' as your plugin landing page for those plugins… If you have access to MyPHPAdmin or something similar, take a look in your BT_plugin table, and look at the value of 'landingPage' for the new plugins 'that dont work' and I bet that if you 'ADD' the value to that field, it'll work. Let us know if that helps! Cheers! -- Smug

Hi Smug, Thanks for the feedback. The landing page had no reference for any of the plugins in the table. The file path is too low for the table and kept truncating. By putting a copy of bt-screens.php in to the plugin folders (with or without landing page field populated) seems to have fixed the issue. Thanks for your insights and prompt response. R., Craig.

Whatever works best for you is usually the best solution… :) but I should say that 'it might be better' if you just entered the value 'bt_screen.php' in the landingPage field of the plugin in question… the reason being, is that although it's a bug, it won't be a bug forever, and it's better to have things 'the way they should be' albiet with a bit of editing, than by circumventing that by placing a copy of bt_screen.php in each plugin directory. There is no 'immediate' backlash, but as things change, those plugins will not avail themselves to any updates provided from the back end… Cheers! -- Smug

Thanks again Smug. I went back in to update the landing page field and some had since been populated after clicking 'check for updates'. I have since checked all for updates and landing page has populated the landing page field for all plug-ins. Thanks again for your help.