kongondo

@desbest...welcome to PW and the forums. Actually, the code in the Blog profile is not really meant for beginners...If you want to learn how to structure your template files I'd recommend these two tuts: http://processwire.com/docs/tutorials/default-site-profile/ http://processwire.com/docs/tutorials/how-to-structure-your-template-files/

Not a straight answer, I know, but here's how we do it in the module Blog

....am curious, why do you need an alternative?

This post is in response to some queries I received about Media Manager. I will be improving the documentation in the next couple of weeks. 1. Edit media details 2. Automatically publishing media on upload

I am back. Might be a while before I go through all pending issues. @gerritvanaaken. The module is not yet PW 3+ ready...but it will be once we have a stable release of that version of PW, thanks.

Am back in play. I am working on the frontend module.

I am now back and slowly catching up with issues. Thanks for your patience. Thanks @Robin S for helping out above. @Jonathan Claeys, many thanks for using Media Manager. Please let me know if you need further clarification. I can confirm that a MediaManagerArray is a WireArray. I have updated the docs to reflect this.

Hi all, I'm going to be away for the next couple of weeks (4-5 weeks possibly) with little if any access to the internet. I will deal with any queries on my return. Thanks

Hi all, I'm going to be away for the next couple of weeks (4-5 weeks possibly) with little if any access to the internet. I will deal with any queries on my return. Thanks

Hi all, I'm going to be away for the next couple of weeks (4-5 weeks possibly) with little if any access to the internet. I will deal with any queries on my return. Thanks

Storage: Stored in page: Yes. Please see the OP, about half-way down Custom fields: Yes if you add them directly to the templates but you will not be able to edit those custom fields using the MM interface. In addition, MM pages are hidden in the admin so editing your custom fields will not be ideal (or accessible to normal users). Alternatively, you can use images/files native description and tag fields. These are currently editable directly in your Media Library. File Usage: It counts the actual usage in FieldtyeMediaManager field in the DB No No

Media Manager version 005 (released (07/08/2016)) Happy to announce the latest release of Media Manager. Changelog Media Manager in Repeaters: Media Manager (Fieldtype- and InputfieldMediaManager) can now be used in Repeaters with full access to your Media Library. Demo video and instructions are here.

Until your question, it wasn't ....I have made some minor changes to version 005 which now enables this. I'll try and commit this today, if not, then over the weekend. Thanks for your interest in Media Manager...

Thanks for the interest guys. I'll have to consider a few potential security issues first then make a decision. No ETA for now...

Media Manager version 004 (released (01/08/2016)) Happy to announce the latest release of Media Manager. Changelog FieldtypeMediaManager/InputfieldMediaManager: Configurable setting to insert media in inputfield and close modal. Set in the Details tab of your FieldtypeMediaManager field Fixed bug where non-allowed media types (for those limiting media types available to InputfieldMediaManager) would still show up in the results in the selection modal. Fixed bug where the menu item 'All' would not appear in the InptufieldMediaManager media selection modal even if allowed media types was limited to at least 2 types By popular demand, a CKEditor image plugin! mmimage (cloned and adapted from pwimage thanks @ryan) lets you insert images in your Media Manager Image Library directly into the rich text editor. See a video demo + instructions here @TODO: Multi-tagging of media Documentation (thanks for being patient with me guys...)

@SoapyDaz. Welcome to the forums I can only guarantee that it works in 2.7x...Others have reported issues regarding PW 3+. I am waiting for a stable release of PW 3+ before I officially support the module for that version.

Thanks for the suggestion. Done!

In the interest of transparency, I would like to state that I made a mistake in editing @Tomasz post. I have personally apologised to him and advised him to use an appropriate board here to air such views. We hope this incident doesn't keep him away from the forums. We are a friendly bunch here but we do make mistakes sometimes. Cheers, Francis

@gebeer...in case it's still of interest to you, I have released a commercial dependent select module.

Dynamic Selects Released 27 July 2016 Dynamic Selects is a commercial module that enables the creation of dynamically related/dependent ajax-driven chained dropdown lists (aka cascading selects) for display and storage of multiple types of data. The module can be used both in the front- (display only) and backend (display and storage of data). Setting up Dynamic Selects is very easy. With minimal effort, site developers can set up simple or complex chained selects. By making a selection in a trigger dropdown, via ajax, values are fetched and dynamically populate options in the dependent select. In turn, making a selection in the now populated select triggers the same action further down in a dependent select. The module only uses/stores ID references to selected options in the selects meaning the most current/up-to-date data will always be displayed in the selects. Currently only ProcessWire managed data are supported. If there is enough demand, we may incorporate external data sources (typically JSON). The module consists of 4 modules ProcessDynamicSelects MarkupDynamicSelects FieldtypeDynamicSelects InputfieldDynamicSelects Video Demo: https://youtu.be/wkhx8xQ5ue4 Documentation: http://dynamicselects.kongondo.com/ Shop: https://processwireshop.pw/plugins/dynamic-selects/ Requires: ProcessWire 2.5 or newer and jQuery if using the frontend module (MarkupDynamicSelects) Features Easily create powerful ajax-driven cascading/chained selects/dropdowns Unlimited number of select dropdowns per field Data-mapping made easy thanks to multiple possible combinations of data relationships, triggers and sources Mutlipe data relationships to chose from ID-based data referencing ensures your data values always stay fresh Remote and local caching to speed up data access and reduce ajax-requests to server User-friendly, intuitive and easy to set up IMPORTANT Before using this module in the frontend, you will need to thoroughly read the security section in the documentation.

...in addition to the comments above, I am not sure anyone attempted to compare RC to ProcessWire. At least, I don't see this in the OP.

@Bryson Brilliant. Glad you got it sorted. Forgot to mention, in case you missed it, the (almost) complete documentation for Blog is here.

Nice one @heldercervantes. Looks like a good candidate for a case study write-up

Hi @Bryson. Welcome to ProcessWire and the forums. Thanks for using Blog. At the moment, the Blog module is not compatible with version 3 of ProcessWire. Once we have a stable release of PW 3, I'll work on making them play nice together. The missing dependency is Fancybox which has been dropped in PW 3/2.8 in favour of Magnific. As for the double/two pages in one, I think you are seeing that because you tried to use one of the site profiles that ship with PW (e.g. default or beginner profiles) together with the demo template files that ship with the Blog module. They will clash. If you want to use one of those profiles, I suggest you copy and paste code from Blog demo template files into the profile's template files. It might be easier though, when installing ProcessWire, to instead use the blank profile. I recommend this to whoever wants to learn from scratch since you are starting off a clean slate. However... Let's start with the basics first. ProcessWire allows you to build your websites exactly how you want them. This means no one template file approach is forced on you. There are different ways to structure your template files as explained in these tutorials. The template files that come with the Blog module and the code in them are just examples to get you started. They use the so-called delayed output. Of course you can choose to use the examples or even start from scratch. What you see in /Blog/template-files/ are its demo template files I refer to above. On install, if you selected to install Blog with the demo content, they are copied over to /site/templates/ Default Name: For security reasons, Blog does not output your name (which is actually your ProcessWire log in name) as the author of Posts. Instead, you need to edit the user and use the Title field to input your author names...e.g. 'Prince Charles'. Sorry, my answer seems to be a bit jumbled up. Here's what I'd advice you though: I suggest you get to know how ProcessWire works first by reading the basic docs, especially how to use the API. Using the Blog module to learn about ProcessWire may be a bit advanced for people new to the system. Secondly, have a read about the various templating strategies. You will then be able to tell where $content comes from :-). Finally, if you have some knowledge of PHP, I suggest you install ProcessWire with the blank profile. It will help you learn better IMHO...I know this is not for everyone, but I like starting from a clean slate. You can then use whatever templating strategy you wish. Let us know if you need further help...