Macrura

the api access to the cassette ui is working for me; you just need to make sure you supply the options, because there is no way to default to the cassette for the player, because it only supports 1 audio file per page..

it means for example if you were linking from a page to a form and what that page reference, you'd echo the url like <a href="<?=$pages->get(9999)->url?>?pageref=<?=$page->id?>">Register Now</a>

not sure, it sounds like $sm2 is not the module instance; you'd need to use Tracy Debugger to bd($sm2) at that point and see if it is actually the module; I will test your code also to see if i can troubleshoot that issue; are you passing any options to the player, or are you setting the default player as the cassette, in the module config?

you have some rules messing up the player; make sure the player CSS is loaded after your site css; The controls shouldn't appear until you hover over the cassette. Problem 1) #content p, #content ul, #content ol, #content table { margin: 1em 0 1.5em 0; } Problem 2) #content ul li { margin: 0 0 0 3em; display: list-item; list-style: none; } problem 3) #content a { color: #f00076; } once those are solved you should have it looking like this: for the other issue, you should check to make sure that the variable $sound is not getting overwritten somewhere; for safety you should probably call it $sm2 instead of sound;

i don't see the CSS file - cassette-tape-ui.css in your header; if you have Tracy, can you try debugging what is inside $config->styles? on my local machine it all works; alternately you can hardcode the reference to the css file on that page, like this: <link rel="stylesheet" href="/site/modules/TextformatterSoundmanager/soundmanager2/cassette-tape/css/cassette-tape-ui.css">

so are you doing this? ) In order for the module to output the necessary styles and scripts, you need to echo the $config->styles and $config->scripts arrays into your site's header/footer. Here is an example: // In Header foreach($config->styles as $style) echo "<link rel='stylesheet' type='text/css' href='{$style}' />\n"; // In Footer foreach($config->scripts as $script) echo "<script type='text/javascript' src='{$script}'></script>\n"; I don't see the cassette css file anywhere on the page; the styles for any given player need to be either hardcoded style link references on the page, or you have to use $config scripts & styles in order for each/any of the players CSS and JS files to load;

what about SSL, cloudflare, force www, are you doing any of those things. Do you have any hooks modifying page path anywhere? Have you tried migrating the site to a different server, or do you have a copy you can test on a localhost?

have you tried using the default htaccess file, that PW ships with?

if the tape doesn't look right you might also have to use this css: .tape * { box-sizing: content-box; } the next version will have that in the tape css file..

once you eliminate the errors, if you want to use that player on a page, for now you'll need to manually insert this code in the header, until i can update the module to insert that; I probably had a cached copy of the swf player on my old dev machine which is why it worked without that.. once the module is updated, then it will insert that code into the header when you have a cassette on the page.. <script type='text/javascript'> var swfUrl = '/site/modules/TextformatterSoundmanager/soundmanager2/swf/'; </script>

swfUrl needs to be defined, since that particular player requires flash; but the strange thing is this used to work on my local but is not currently working; i will check and see if there is some way of getting it to work again... also on your page jquery isn't loading, because of Blocked loading mixed active content

The admin search is JqueryUI Autocomplete. http://api.jqueryui.com/autocomplete/ there are some Extension Points such as _renderMenu and _renderItem that are using some custom logic to return the required markup. (look at the AdminThemeUikit/scripts/main.js, as well as the _search-form.php. It does work well and looks nice, but can achieve the same basic look and functionality for a front end site with possibly less work using typeahead.js and with the Bloodhound using local storage, it could mean for faster lookups.

sounds familiar; I switched some sites over to a KnownHost VPS and so far it has been good. I can definitely say that their support is great, any support ticket is answered very rapidly, and this applies to both VPS and for their shared hosting plans.

i just use a function to output the code from realfavicongenerator function favicons($options = []) { $defaults = array( 'appleColor' => '#4d9db4', 'msColor' => '#da532c', 'themeColor' => '#ffffff', 'path' => null ); $options = array_merge($defaults, $options); $folder = 'site/templates/favicons/'; if($options['path']) $folder = $options['path']; $folderUrl = wire('config')->urls->root . $folder; $filePath = wire('config')->paths->root . $folder; if(!is_dir($filePath)) return; $out = <<<OUT <link rel="apple-touch-icon" sizes="180x180" href="{$folderUrl}apple-touch-icon.png"> <link rel="icon" type="image/png" href="{$folderUrl}favicon-32x32.png" sizes="32x32"> <link rel="icon" type="image/png" href="{$folderUrl}favicon-16x16.png" sizes="16x16"> <link rel="mask-icon" href="{$folderUrl}safari-pinned-tab.svg" color="{$options['appleColor']}"> <link rel="shortcut icon" href="{$folderUrl}favicon.ico"> <link rel="manifest" href="{$folderUrl}site.webmanifest"> <meta name="msapplication-config" content="{$folderUrl}browserconfig.xml"> <meta name="theme-color" content="{$options['themeColor']}"> OUT; return $out; }

you might be misunderstanding this. Context help for templates means you need to add a template select field to the page holding the content to be shown on that template. Notice how you are missing that whole setting - you need the fieldtype, then the field and add it to the doc page template, then select the template where to show the doc.

i understand it may be more work, but as far as i know there is no way to magically create virtual admin process pages on the fly, each 'page' in the admin that you want to be viewable and access controlled needs to have a real page.

you need 1 process page for each displayable doc page.

@jmartsch (1) did you select a page to display and is the field containing the content populated on that selected page? yes, it is, but you'll need the other module, called ContextHelpTemplate, and that module can work with PD https://github.com/outflux3/ContextHelpTemplate

did you set the enclosure field in the module settings; i know the module says you can set it from the api, just wondering what effect that has; also make sure the feed is not cached...

one of the great things about ui-kit is the namespacing; you always know which classes are controlled by uikit, and if you namespace your custom css/overrides it's clean and easy to see what's going on...

looks correct ?

yes, you need to enable URL Segments on the homepage. then, if you do the hook, when you click "View Page" from the editor, it should go to the new URL off the root. So if you have a page that is posts/name-of-page, that would now be /name-of-page

I use DBPowerAmp for ripping, there are a lot of advantages to using that, it handles cover art fetching very well, and the accurate rip is also very useful

sure, no worries, i wish i did know how to do it, but we've never had the need for that yet, but it may be required in a project soon..

i haven't integrated PW with Foxy, in terms of users..