Strange one this, killing me since I got up this morning. Re-installed 3.0 on GoDaddy this morning, everything worked a treat as always. All 78 or so plugins are fine it seems, all updated and playing nicely. Except that is for menu_with_image and (don't laugh) MacImageGallery. It isn't a problem with the plugins per se but more to do with my hosted environment. I can add these plugins (they show as being up to date etc 1.4 and 2.5) but when I click on the screens to add to them via the buttons on button menu I get a 404 error. So I deleted all the instances of galleries in my apps and deleted the plugins and re-installed, same thing, 404 error. Apps download, run and compile, everything works apart from this. Back to dig, any ideas anyone? Going round in circles here for close to 7 hours. It's something I've done but can't figure it out.

This is not just you, same here, and I've been contacted by a few people who have the same issue. If I'm right, your 404 URL is when you try to access a link something like: http://myserver.com/server/bt_plugins/menu_list_simple/indessdasdas Right? Wrong? Still investigating myself. David https://www.buzztouchmods.com/market

Correct. Yip. Most seem to work. So I am running 12 menu items from a home button menu. (not that is really the issue but...) I get this (like you said) when I select the gallery from the button menu admin screen: http://www.myserver.com/BT-Server//files/plugins/macimage_gallery and http://www.myserver.com/BT-Server//files/plugins/menu_with_image Been looking at the DB to see if I made a donkey of something during server and plugin install and update. So far have I managed to kill a few screens in a live app so it's back to the drawing board for a bit. What are you thinking?

Maybe your .htaccess file is playing tricks on you.

I find it very odd. I did a little research, and found that there is a field in the plugin section of your BT_Database called 'landing page'. In 'most' of them, I see an entry for 'bt_screen.php'. For those that have the entry, things work dandy. For those that don't, you get 403 or 404 errors. Not sure completely 'why' some do/some don't, but that's 'what' is going on. Cheers! -- Smug

Been looking through the DB through a glass of Merlot. Good man Swug! Off to look.

I'm a little surprised at you. 'Best Practices' clearly recommends a chardonnay… Cheers! -- Smug

Here is what it is as best I can figure out… The new plugin format is different than the old plugin format. Our biggest indicator is the lack of an index.php file. Old plugins have them, new plugins don't. Supposedly, 'new' plugins, when entered into the DB should have the 'landingPage' field populated with the value 'bt_screen.php'. Old plugins of course, will not. But, they will still retain their old index.php file. So, with a bunch of old and new plugins, we need to figure out which is which… so there is a part of the 'bt_screen.php' file that parses this… sort of a 'if they have it, do this, if they don't, do that…' sort of statement. But 'those that dont' are considered 'old plugins' and it's thinking there should be an index.php file around… but there isn't. The thing is, some 'new' plugins don't have an index.php file, but are being treated as an 'old' plugin. I haven't been able to figure out why just yet… Cheers! -- Smug Edit: The quick fix for self hosters seems to be adding 'bt_screen.php' to the landing page field of your plugin table, providing the plugin really 'is' BTv3 compliant. It might be that some missing component in the package led the plugin to be considered 'old school'.

One quick thing. If you're self hosted, and you have access to phpMyAdmin or some similar administration tool, you can quickly add "bt_screen.php" to all of your plugins with this solution. Login to phpMyAdmin. Open your BT Database. Open up an SQL query window Paste this, substituting your BT Self Hosted field name if different: UPDATE bt_plugins SET landingPage = 'bt_screen.php' and hit 'go' or 'execute' or whatever your interface uses. It will populate each 'landingPage' field with 'bt_screen.php' in your database. Make sure you actually have BT v3 plugins. Cheers! -- Smug

It's playing around in phpMyAdmin that got me in trouble in the first place. It's a weird thing for me I'm afraid and deeper than the landing thing I fear although connected. Plugins, well screens can be selected without issue on the list or grid view but when are selected from within an other menu system triggers the error. Got most of the plugins available all updated but think I was distracted and deleted plugins that I had in use that sent it on it's current cycle. Reckon the following would kill it due to the mix of new and old, no? UPDATE bt_plugins SET landingPage = 'bt_screen.php' What do you think of wiping the plugin Database table and then deleting and re-installing all the plugins.

Thanks for the SQL query Smug, you're kickass! Make sense that this can't be fixed on BT's end by us, you should point David this way, but not today, I have a feeling he is busy today ;-) Cheers, David https://buzztouchmods.com/market

I physically removed my plugins, refreshed and re-added from my BT Account. Mine came out with 'some yes, some no'. which led to my sql venture… I don't know if wiping the db will help, but my first instinct is no… I know running that little sql query worked on mine… as long as it has a landing page, it works… Cheers! -- Smug

Appreciate all the input Smug. Ran the query now plugins that do have landing pages such as carousel error out. Weird. I did the same as yourself this morning, physically removed plugins, re-added 74 from my BT account and bam.

All plugins that have landing pages error out? Cheers! -- Smug

Smug- You are absolutely brilliant!!! *************************************************** Login to phpMyAdmin. Open your BT Database. Open up an SQL query window Paste this, substituting your BT Self Hosted field name if different: UPDATE bt_plugins SET landingPage = 'bt_screen.php' and hit 'go' or 'execute' or whatever your interface uses. ***************************************************************** thank you for this fix!! Dave

Awesome Smug, just on time!! Thanks

Thank you! I had to go into the db and do it by hand. LA

Smug, you are such a treasure! I had this problem today with a new plugin, I did a Google search and found this forum post, and problem solved! Thank you, Smug!