Leaderboard

This Textformatter allows you to designate areas in a single textarea to be converted to a collapsed accordion list. The markup pattern for this module is based on the Pagination Textformatter module with the idea that they could be interchangeable. Github Page Simple Demo To define an accordion item Put 5+ hyphens '-----Your Title Here' on a single line (within paragraph tags) to specify a title for the accordion item. The paragraphs below will be collapsed. This is the same idea as the Pagination Textformatter, however titles are not optional. If you just put the dashes, the item with be automatically titled "Untitled". To end an accordion To end a group of accordion items and return to regular textarea content, put exactly 5 slashes on a single line '/////' (within paragraph tags). This is only needed if you want to end collapsed content and return to regular textarea content. Notes I've been using this on a production site for nearly a year, but before Ryan released the Pagination Textformatter it was using with a totally different markup pattern to designate the accordion items. It should be pretty stable, but consider it a beta release. Markup pattern inside a textarea (Nearly identical to the Pagination Textformatter) ----- Accordion Item The paragraphs beneath each accordion item are collapsed by default and open when you click on the title specified above. You can use multiple paragraphs, and any other content allowed in the textarea. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec odio. Quisque volutpat mattis eros. Nullam malesuada erat ut turpis. Suspendisse urna nibh, viverra non, semper suscipit, posuere a, pede. ----- Another Accordion Item Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec odio. Quisque volutpat mattis eros. Nullam malesuada erat ut turpis. Suspendisse urna nibh, viverra non, semper suscipit, posuere a, pede.Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec odio. Quisque volutpat mattis eros. Nullam malesuada erat ut turpis. Suspendisse urna nibh, viverra non, semper suscipit, posuere a, pede. ///// The 5 slashes above signify an end to the accordion group above. You only need to specify the end of a group if you want to return to regular textarea content. You can continue to use the same pattern to collapse content into accordions as many times as you wish. Results in the following markup: <dl class="accordion"> <dt> <a href="#accordion-item">Accordion Item</a> </dt> <dd> <p>The paragraphs beneath each accordion item are collapsed by default and open when you click on the title specified above. You can use multiple paragraphs, and any other content allowed in the textarea.</p> <p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec odio. Quisque volutpat mattis eros. Nullam malesuada erat ut turpis. Suspendisse urna nibh, viverra non, semper suscipit, posuere a, pede.</p> </dd> <dt> <a href="#another-accordion-item">Another Accordion Item</a> </dt> <dd> <p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec odio. Quisque volutpat mattis eros. Nullam malesuada erat ut turpis. Suspendisse urna nibh, viverra non, semper suscipit, posuere a, pede.Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec odio. Quisque volutpat mattis eros. Nullam malesuada erat ut turpis. Suspendisse urna nibh, viverra non, semper suscipit, posuere a, pede.</p> </dd> </dl> <p>The 5 slashes above signify an end to the accordion group above. You only need to specify the end of a group if you want to return to regular textarea content. You can continue to use the same pattern to collapse content into accordions as many times as you wish.</p>

I just finished this article and wanted to post it here as I'd love to get some feedback from you guys in the comments of the article explaining why you work with ProcessWire. There's a great chance here to help spread the word a bit more for this awesome CMS we all love. If you have five minutes, please share your thoughts in the article comments. I'd appreciate it. ProcessWire vs WordPress

If anyone is interested, this is a realtime commenting system I'm implementing using it. It's very alpha and I'm not sure if I'll ever to publish it as a module, but it was very easy to implement. The comments are posted using AJAX and the simple api router I use calls a function to post the comment. This function in turn creates a Pusher event in PHP and sends the data to Pusher, which sends it back to the client (this is all push). There are a few lines of javascript waiting for the event to trigger, which in turn renders the comment that was send back from the server through Pusher. I'm using all native PW fields and templates for this, this allows me to have caching enabled on the server. Each time a comment is posted, the discussion is re-cached, so if someone loads a page, it should get most of what's supposed to be there, then any updates are done client-side.

There are multiple strategies you can use. A lot of times, the problem with clients is cash flow on their side. They will see this 4000$ bill and tell themselves "there's no way we can pay this right now". If at all possible, look at payment options. Do you specialize in a specific market? This could help word of mouth referencing and you can develop ready-made modules and templates you can start with, instead of starting from scratch every time. This could help you reduce development time while keeping the same salary (you're selling value, more than time!). It might be interesting to offer both time- and non-time-based contracts. You might have 6-7 websites to do in a month, all requiring tops 2-3 days of work but still have enough cash flow to pay bills and luxuries. If one ever takes a bit more, the loss you're making there will be compensated by the others. I don't know how you manage your projects, but scope limiting can also help you gather contracts (the ones who pay less could cut on features). The problem is that you then have more contracts but sometimes they're too small to be worthwhile.. Try looking at having a few retainers. Bigger customers are more encline to have retainers and are typically those who'd have more money too for tailored websites. This is a plus, but retainers are harder and harder to find it seems. Or you might be interested to join a startup and create larger size projects. There's a few options out there, I'm sure there's more..

Should be: $pages->get("/about-us/meet-the-team/")->children("include=hidden"); since the children are hidden and not the parent. And also I prefer to get the parent by id since changing the page name would make your selector return nothing. For example if your team page has id 1020: $pages->get(1020)->children("include=hidden");

Here is a website I nearly finished(Still waiting for decent photos from client for gallery) for a hairdresser in Slovakia so it's all in Slovak. http://www.milujsvojevlasy.sk/ This is the first site that I used profields. I used pro fields table on the price list page: http://www.milujsvojevlasy.sk/cennik/ Using Profields table made it really nice and simple for the client to update prices in the admin. For the booking system I integrated a separate script. Used my own grid system / framework http://www.cutegrids.com to make it responsive. and of course built using the fantastic Processwire and Profields.

Here is a companion module (my first public module). Accordion Textformatter I've had this kicking around for a while. After you released Pagination, I figured I would update it and get it out there. Same idea essentially, but creates collapsed "accordion" content instead of pagination. Hope you don't mind, I leaned heavily on some of your code for the markup pattern. I wanted to make them essentially interchangeable (not that you ever would).

Yes, you can upload the same image as many times as you want Srly now, you can't use an already uploaded image from a field because images have a 1/1 relation with pages. This makes the system behave in a simpler and safer way, and there is not the risk of making images that are being used by a page from disappearing when their original page is deleted for some reason. If you need the same image in two different pages, the best bet is to re-upload it, and have two copies in the system. You can always reuse images from the templates by calling the page where they are in. This was discussed already some times but I don't have the time to search right now. You might want to search a bit in the forum to find some interesting discussions on this subject.

That would change nothing since the children() needs the selector. and include=all would also include unpublished children which I guess is not desired.

by members of the community with perfect pw-integration: https://minimize.pw/

This is an inputfield module integrating Trumbowyg WYSIWYG editor into ProcessWire, quickly hacked together after some discussion at the Redactor thread. Trumbowyg is a light-weight alternative to more feature-rich editors, such as CKEditor or TinyMCE. Both this module and Trumbowyg itself are still in alpha state. Customisation options include only a subset of what Trumbowyg provides, more will be added in the near future. Also, link and image features as seen in other RTE modules (TinyMCE and CKEditor) are not implemented yet. The module is available at https://github.com/teppokoivula/InputfieldTrumbowyg.

This Textformatter module for ProcessWire enables you to break up a single textarea field (using either TinyMCE or CKEditor) into multiple pages. You include all of the content in a single rich text field and separate each pagination with a line of hyphens (5+). When rendered on the front-end, the user will see pagination links at the bottom of the page enabling them to move forward and backward through the content/article. Also included is the option for title pagination. That means assigning a title/headline to each pagination and giving the user a list of those titles they can click on to move to each section of the article. Example of this module in action Documentation and customization options GitHub Page Module Page Download ZIP Install class: TextformatterPagination

If you look for CSS “regressions”, my first thing to check out would be if all floats are cleared properly, if there's any “strange” positioning involved. Maybe to test it, temporarily deactivate CSS altogether or very selectively for the pagination using the browser's dev tools. If the pagination links are there and the markups looks the same, it's very likely some CSS issue.

Hi Adrian, I don't know if you could do that as a pure CSS solution, you would probably have to use JS to check the window width and then swap the .accordion class with a .tabs class. Seems doable, I've styled a <dl> into tabs before (can't find the tutorial at the moment). I've never tried to do pure CSS tabs, but that would be the easiest way if it's possible. I don't have much time to develop this further, but if I can find a need for it here at the day job I might be able to devote some time to your request.

Nice! How about an option for tabs vs accordion, and maybe the ability to switch from tabs to accordion automatically on phone sized devices?

Nice on Tom!

I think this was fixed here: https://github.com/pine3ree/ProcessWire/commit/8cc1bcccaaf717871a7173b7cbc3fe2e8552afc7 and discussion here: https://github.com/ryancramerdesign/ProcessWire/issues/547 So please try the latest dev and see if it works for you now

Also no hidden pages in the result ;-)

I guess Teppo is on holidays

10-15 seconds is adjustable. This is default settings. You can make it smaller or bigger depending on amount of spam or attacks your are getting. Setting it to very small value will still deter many bots who do not run Javascript at all. Now regarding waiting. Just registering on this forum to answer in this topic I had to answer question, enter reCaptcha and wait for validation mail. both took definitely more than 15 seconds. I would say it make sense to set complexity (i.e. amount of work necessary) dynamically based on what form is that (i.e. make it harder on registration form,) what is user level on forum is (if they have many posts - make complexity minimum or remove it altogether,) etc. I just started this project and gathering feedback. I am already implementing some features people asked for, so feel free to ask questions please As for bitcoin mining - you are very close. It is actually dogecoin proof-of-work. Basically idea is that each interaction you do with website cost you something. Once I understand that each interaction I do comes with cost - I would think twice before posting junk. And obviously it makes job of bots even more expensive, since they need to post tons of spam to get their rankings/leads/subscriptions. Anyway, if someone have questions - I am always available at pavelkaroukin@gmail.com

I would support you if any possible. Would love to have a stable shopping system on PW base (including, taxes, currencies, different porto, etc.). Maybe we could just start with making a list somewhere to collect stuff that needs to be included and stuff that could be included (like stripe checkout or stuff like this). What do you think? Btw.: I really often need to implement a shop so this would be really great. Maybe we could even raise some money if this allows you to put more work into it (Going to write you a PM)

Solved with 777 on the sessions folder and all contents. I seem to hit this (it feels) every time I make a site live :/