Jump to content

Macrura

PW-Moderators
  • Posts

    2,756
  • Joined

  • Last visited

  • Days Won

    40

Posts posted by Macrura

  1. For anyone using this (not many i guess), I have updated the module for compatibility with newer versions of PHP.

    https://github.com/outflux3/TextformatterBBCode

    More info at the repo, but in short, this uses the new Vanilla Forums maintained version of Nbbc. The module is also PW 3.x only, as it uses namespaces.

    One item of possible interest to module developers in this version is the use of the composer file loader (https://github.com/Wilkins/composer-file-loader) which allows the vendor folder to be loaded without any modification, and without needing to use Composer, sort of an on-the-fly package loader...

    TL;DR:

    With any newer version of PHP, and where the current/old version of module is instantiated, the following error was occurring.

    PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; BBCodeLexer has a deprecated constructor in .../site/assets/cache/FileCompiler/site/modules/TextformatterBBCode/nbbc.php:67
  2. So the issue is simply that in multilanguage environments, it seems to behave differently; all you need to do is change the value from "0" to an empty string and it should solve this. I will update the kitchen sink example to fix this in multilang environs.

    it should be pointed out that what this module really does is to basically use all core functions for rendering the fields; So in this case the issue was really stemming from how the field was being defined, and we didn't catch it because we didn't test the kitchen sink file in multilang.

  3. strange that you'd be running SF 1.0.3 as the 1.0.4 version has been out for over a year- can you double check it is version 1.0.4?

    This is the 2nd report of this issue, and i have not been able to reproduce it – are you using the kitchen sink JSON or PHP version (shouldn't matter though).

    If I can reproduce this, i think it can be fixed - but i'm not clear where to look;

    I guess once you confirm it is 1.0.4, or upgrade to that, if the problem persists, i will keep trying;

    I'm running tests on PHP 7.3.1, PW 3.0.148, MySQL 5.7.25

     

  4. 7 minutes ago, Jens Martsch - dotnetic said:

    Right now, it seems, that I have to use $panels->add for every single panel, is that correct?

    i agree here with this – i actually tried to add an array of panels first before I realized you had to do each panel on a different call..

    • Like 1
  5. @HMCB, thanks! So the datepicker itself is nothing fancy, it's just a style-matched version of Calendario

    https://tympanus.net/Development/Calendario/index2.html

    In Calendario, you just setup a JSON array of the events, and init the plugin with JS. The link on each date is to a URLSegment which then is processed via the API to get the events for that date. The URL segment logic was tricky because there are events with series dates (using a ProFields Table) which also need to be accounted for, but the beauty of the PW api is that it only took maybe 20 lines of code for all of the event fetching logic for single date calls.

    ----

    also wanted to say thanks for the mention on the blog, newsletter, and SOTW! ?

    ----

    and the SkyscrapersTurbo™ Profile is well underway, featuring rangesliders for all numeric attributes (Year, Floors, Height) and architect filter. So this version is is possible to narrow down results for very specific combinations.

    • Like 6
  6. @Vigilante, sorry to hear about that; Probably best to just remove those 2 fields from the kitchen sink file. I'll run a test here to see if those are caused by any recent changes in the fields or admin.

    Also, FYI, the reason those show up everywhere is that settings are stored in module config and those do load in the admin; So for example if you have invalid JSON you may see an error everywhere....

  7. thanks - and i guess the version file needs to be updated (?)..

    this is working well for me; I have my own dashboard module, but it uses templates, pages and fields, and is thus cumbersome for smaller/low budget sites. My dashboard module uses AdminLTE, so it has stuff like collapsible panels with state recall; For some of the more complex panels like Formbuilder entries, etc, i'll just build custom panels and hook into this module.

    Thanks again for building this! This is very extensible, looks and works great, and seems like it will be a very popular module! Here's the dashboard i just threw together...

    Dashboard_ibtc.thumb.jpg.92f7b9d64667983954227234848e5448.jpg

    • Like 9
  8. On 12/25/2019 at 3:20 PM, 3fingers said:

    I'd love, as a christmas present, and in-depth tutorial/guide on this subject (since, IMHO, you've made the best search pages throughout the years) ? ?

    possibly the easiest way might be for me to get the skyscrapers demo database and then just build the Datatables version of the demo site, skyscrapers list with all of the instant filtering, and the addition of the rangeslider. I'll see if i can get hold of the data, set it up and put on GH.

  9. thanks @d'Hinnisdaël so i have this working on a site, but i have a question about the shortcuts, how do you make a shortcut to a custom URL, like say a module edit screen, or even an external URL?

    Also, how did you get the icon for the Profile to not be a bookmark?

    Lastly, I noticed that I had to put the hooks in ready.php, they weren't working in admin.php for some reason...

    Also, i think there needs to be a fix for the loading of the module only in admin, may be loading stuff in $config without checking if admin and frontend that use $config->styles might be picking those up (i'm getting errors as i have modules that put css/js into $config only for front end)...

  10. @bernhard, many thanks for trying out the module, and for your suggestions and feedback!

    I will see about implementing the suggestions, especially linking to the Github and Forum topics for anyone who installs it, so that it is easier to grasp how to use it.

    I'm also hoping to test out the ImageReference field within this and then post example screenshots showing an even more kitchen sink setup, with images etc.

    Not directly related to your post, but responding more to the general consensus on where and how to create settings pages: I found this module to be most useful in the past couple of years for things like:

    - Site Schema for a person or business (the fields basically follow the schema.org items; See screenshots below)
    - Settings for various custom implementations - e.g. api keys, urls, enable/disable features, etc.
    -- on one site we use this to enable the site manager to choose which comment system to use (Disqus, Facebook etc), and then put in various settings if using Disqus (user id etc)
    - Theme settings, like you might find on a WordPress theme, stuff like colors, what type of global footer to use, logo selections (using page refs), site title, slogan.

    It is also a good way to have settings for any custom code you are doing without having to write a module...

    324647347_Local_Business__schema___ProcessWire__inbalancetaichi_com.thumb.jpg.1eaa4646b7c945e59f2f8570faa8b62f.jpg1348105684_Local_Business__schema___ProcessWire__inbalancetaichi_com.thumb.jpg.018a696581d92c4a4399215d55238052.jpg

    • Like 3
  11. sure, here is the page table;

    the fields on any given section are just like title, headline, body, images, page select, section options etc, plus "section type".

    Some sections have no configuration. The slider section allows the user to select which slides to show; the slides themselves are stored in a central media library, and the settings for any slide are stored with the media item. Sections with images have a field to select the media item to use for the image, or upload an image.

    For a site like this, every image needs to be cleared and licensed, so the media library provides that functionality, with fields for license type, photopgrapher, sources etc.

    874628991_Edit_Page__Home__aaroncopland_com.thumb.jpg.494e3b5619637c8d2226602d43d7a1e0.jpg

    I'm not using the MicroContexts on this site;

    that module is now called "Page Field Contexts", and it enables template contexts based on Page Field values. 
    It's a super simple, yet effective module and I'm using it on several sites.

    https://github.com/outflux3/PageFieldContexts

    • Like 3
    • Thanks 2
  12. 8 hours ago, bernhard said:

    I wonder what the menu items / colors stand for? I guess they have a meaning? Maybe you could add a description on hover of the icons (title tag)?

    I wanted to do a search like Ryan has for the PW site, and might switch over to something like that anyway if i can figure it out. The results really should be sorted into separate lists with headings, which makes it the most user friendly.

    But the ajax/TT search that I implemented was done as a sort of pro-bono sub project, for my own amusement, and as such i could only go so far with it before it taking up too much time... Hoping to work on a replacement for it or improvements during the support months coming up...

    yes the colors and icons do mean something, but i don't know if you can have a tooltip on an already hovered item, seems like hover inception-ish...

  13. 21 minutes ago, dragan said:

    Most fancy out-of-the-box austosuggest widgets have accessibility problems, Typeahead is one of them. It's a known issue, and there seems to be a fork with optimizations. The UK government has built their own version.

    cool, thanks for the info. Expecting to do some maintenance on this starting in January, so I will put this on the roadmap.

  14. @3fingers, sure - thanks for the kind words!

    In terms of a guide/tutorial, do you mean the Twitter Typeahead search on the inputs, or the table/filter on the listing, or the site search, or the advanced music search...(lot of searching going on here)..

  15. Sure! In terms of the visual/layout stuff, this is the first or 2nd site I did with UiKit, switching from mostly using Bootstrap. I ended up using a lot of the built in UiKit features, it really made the experience of doing the front end a lot easier and provided a lot of the inspiration for how stuff was setup.

    In terms of the api/php, there is a theme module which handles basic theme/template related stuff, and a meta module which handles all of the meta elements in the head (page titles, descriptions, open graph, schemas etc.); It amounts to a frontend api, inspired by the pw api. I can go into further detail soon...

    In terms of how the site's page content is managed, every content page is using simple PageTable with configurable sections as the page table rows.

    the most challenging part of this site was the works database and the way the works relate together at various levels...
    It also took the content editors over a year to proof the works listing.

    The events were also a lot of work; Those pull in automatically from the publisher's webservice using SOAP...

     

    • Like 8
×
×
  • Create New...