Joss
PW-Moderators-
Posts
2,875 -
Joined
-
Last visited
-
Days Won
47
Joss last won the day on February 1 2017
Joss had the most liked content!
Profile Information
-
Gender
Not Telling
-
Location
UK
-
Interests
Music, Writing, Web Technologies, Copy Writing, Cooking, Allotment, Surviving, Politics, more cooking, writing books
Recent Profile Visitors
27,805 profile views
Joss's Achievements
-
Dedication I call that! The cause will be delighted... 😄
-
Update: WARNING!!! Serious Mission Creep has been spotted. (Which is rather fun). I am currently developing the other components complete with permissions etc so that they all work in a similar fashion. And I am creating a unified Page Library field which can hold all component media - images, files, links, embeds, content, etc - then make them available to the new unified TinyMCE EMM field. (Click in an insert point, press the EMM button, and decide what you want to insert). The field will also allow the creations of outputs - single image, gallery, multiple links with icons, content, whatever - that can then be called into the template in a similar way you call in a subpage or alt text form an image, etc. Devs will have the choice of using either single and multiple EMM fields like they would image fields - nice and familiar. Or using this new method. Let's hope it bloody works and don't have to quietly delete this post in embarrasment........
- 5 replies
-
- 3
-
-
-
- module
- file manager
-
(and 1 more)
Tagged with:
-
Just tarting that bit up. Initially it will tell you how many pages an image is used on. You can then expand that into exactly what pages those are. Also, since editing images create a family of variations, it takes that into account or shows just for that variation. I am trying not to drown an admin in statistics, while leaving them the option of doing exactly that if they feel so desired.
- 5 replies
-
- module
- file manager
-
(and 1 more)
Tagged with:
-
Joss started following So, Bing/ChatGPT and Processwire? and Essential Media Manager
-
A new module, coming soon (with any luck and a following wind!) This is a module I am developing initially for my own use in a couple of projects next year. I am making it now because these are long running projects, and though they may not see the light of day for some time, some of the content will need to be worked on far sooner. For these, I need central media management, primarily of images, that works in a way that suits me. So it seemed easier to start from scratch than break someone else's. Two big disclaimers first: I have designed and specified every nook and cranny with my own needs in mind. The brief is turning into a book. I HAVEN'T CODED ANY OF IT, apart from create the odd directory. It is built with and by codex, with me waving a baton at it and pointing out bits of PW functionality it can use. So we will see how that works out! As the title suggests, it is a media management module which centralises everything media. It is not, strictly speaking, a replacement for the brilliant PW image way of working, and the two can co-exist without talking to each other. However, this is most suited for a new site where this is the only way you will deal with images. Otherwise, it will be a lot to get your head around! Why make life hard? For now, here is a list of features in no neat order, but just as I remember them when typing. Every file has its own page Categorisation is by multi-tag only It comes with a central library manager with a multi or single uploader It has "Components" which deal with different types of media in the way that suits them most. Images, Other files, Videos and Audio, Embedded audio links, Authorised external links, content snippets etc. When you install, you can choose which components you want. Or you can add them on later - it won't install all their functionality till that happens. It comes with an all-singing and dancing EMM field. For images, this works like a multi-image field, a single image field, and it installs into TinyMCE. For other types of media, it does it's own thing. The EMM field acts much like the PW fields, except all images etc are stored centrally and managed centrally. Images can be edited via the EMM field - nothing flashy, but all the standard PW bits, etc. That has a pretty interface. Editing creates variations so the original remains untouched. These variations are grouped into families. Images and other files can have multiple fields associated with them (or not if you don't want), including meta data drawn from the image. Or not. It is all customisable. For instance, if one of your editors uploads a batch of images, you might require them to fill in certain fields before the image can be published. (Images are kept in a non web root directory where possible until they are published.) Default text can be set for fields. This can be overwritten on the local page where the field is used without changing the original. You can go nuts on fields and make it a complete nightmare for your editor if that is your desire! Permissions. You can create roles with different permissions to the super admin. It will come with a couple of starter roles you can install with permissions. You can create new ones or customise these. (This is possibly overkill, but worth writing in just in case someone wants to use it on a huge site somewhere). The library is built, so it works with the normal PW admin UI, but I am also going to do my own sleeky thing. You can switch between them to your hearts content. Everything is cached, of course, and works with ProCache. There are probably far too many settings, but it will work out of the box without touching them. The EMM field also comes with the ability to add a gallery/carousel thingy without having to add anything to your template. It also has instructions if you want to add your own gallery/carousel thingies and then switch between them. TinyMCE will work with both the PW Image button and the new EMM button, but really, you want that? So the installation also deals with how to change it and what the implication for running too much at once that has the word "image" in it is. Anything else? Content snippets are basically block things that are a bit json-ny in character. They are primarily aimed at the new text editor I (I mean, AI) have built, which is also json-ny and rather likes blocks and snippets. But these will also work elsewhere and can be managed and assembled in the EMM library. (If that is the only component that interests you, then only install it for that!) The UI is still taking a bashing from me, but there will be lots of draggy-droppy kind of things going on, like changing image orders for a gallery and so forth. Lots of inline editing too, to keep things moving. Basically, two sites that I will create to back up long running projects will need to re-use media and information in countless articles. So this is what this is designed to do. It allows me to re-use and vary images and content while keeping track of which pages they are used on, and how they have been used. Centralising everything makes that a lot easier, while not effecting the standard tree like structure of ProcessWire which my brain is comfortable with. I am documenting as much as I can and will give directions on how to add other functionality or possibly even your own components. Or third party modules of course. Now the good and iffy news. Good: This will be free for anyone to use. Iffy: I am not supporting it in any way. I am not in the position to maintain it or support it, so charging for it makes zero sense. It will be on GitHub for anyone to fork and customise. If you love it and it changes your life, feel free to buy me a Landrover. A comfy one. Or a coffee, as the saying goes. Though I would love the landrover.... I will update this page when it is up. Joss
- 5 replies
-
- 6
-
-
-
- module
- file manager
-
(and 1 more)
Tagged with:
-
Rapid — EditorJS block editor fieldtype for ProcessWire
Joss replied to maximus's topic in Modules/Plugins
How is the project going? I have been looking at Editor.js myself as it suits one of my projects. It also fits neatly with a media management system I am doing including reusable content. -
@ryan - On a slightly different note, I have just installed the qwen-2.5-32b instruct, and it is running fine on my system via ollama (better at balancing tham LM Studio, it appears). But I have been setting it up for gramma checking, using modelfile to customise it. Basically, it tells it to act as an editor, not to get too creative, then gives some specific instructions over strange words, grammar, etc. It then creates a model for just that purpose. Could something similar be run for AgentTools so that the actual model has specific hard-wired PW knowledge in advance? I don't know enough to say if this would speed things up or anything like that. But it certainly helps with Word as it knows in advance character names etc, without it having to be prompted at the time.
-
Head north about a thousand miles.... 😀
-
I select an image, click on submit. It sends me to this screen: So I choose a file again (this is a nice small file) and click on Continue and end up: It doesn't like me!!! This is what I was trying to upload:
-
The error that came up during install was that makedir failed to create /site/assets/at/jobs/done, and failed to create the htaccess within "done", and the same with "failed", "pending," and "running." Note - I am using laragon on windows 11 rather than a unix server.
-
Well, I might just be back a bit too. But I have a problem. I decided to update my little profile photo. It happily got rid of my old one, but won't let me upload my new one!!!!! Grrr. And so good to see my brother in fantasy @Soma back amongst the brave!
-
@ryan that is exactly the one I have been playing with today. The 14b version. Unfortunately, qwen 3 coder only comes in 30b and 40b, which is pushing it for me. I might try it again with Ollama. It suffered with LM Studio, but Ollama is meant to be better at dealing with local problems like not having a huge stack of GPUs lying around! The hard bit is the prompting. I was trying to get it to do a very simple page. Create a data set, then search it and spit out a single result. It was determined to ignore the search result and just loop the dataset. Grr! EDIT: By the way, when I installed, it failed to create the subdirectories in jobs. I have hand created them and copied the htaccess file from jobs into each one. Is that right? Anyway, here is the reason for the large box, and the view out of my studio window! Let me know when you start a podcast and need an editor!
-
Thank you, kind sir! (The Pirate bows!) I will have a play. I have been using qwen instruct but also have a few other models. I am a little limited because I only have an RTX 5080. Google's AI swore blind I could run a 31b model with a fair amount of offset (I have 128gb Ram), but I last saw the machine crawling out from under the desk, sweating and groaning, so I am playing with the 14b instead with 1.5b for autocomplete! I will get there. Honest! I still guess at all this stuff.
-
Hi Ryan! Will this, or something, talk to Visual Studio Code via Continue and Ollama? (I have LLMs locally). I am still trying to get my head around what is possible for site development with AI and Processwire - not helped that I am so out of date now!!! Joss
-
Weekly update – 28 October 2022 – TinyMCE Inputfield released
Joss replied to ryan's topic in News & Announcements
@ryan Ta! Since I am in very early dev, I added the line to the config (I didn't have a dbCharset in there) and then duplicated the field. That did it.