-
Posts
7,529 -
Joined
-
Last visited
-
Days Won
160
Everything posted by kongondo
-
@opalepatrick Not everyone knows of Soma's form-process.php. It would have been good to provide a link and/or some code. Secondly, if that link is a thread in the forums, then it would actually be better to post your question on that thread rather than start a whole new topic - it helps with context and continuity..
-
Nice one Brent! I am a sucker for soft subtle colours
-
At the end of the day, when it comes to public voting, I think such contests are really judging assessing popularity rather than 'best in its class' which is a rather more difficult and nuanced concept to assess. So if 10 people like/vote for Joomla and 2 like/vote for ProcessWire, does it mean that Joomla is 'better' than ProcessWire? Not necessarily. Does it mean that Joomla is more popular than ProcessWire? Probably.
-
Yeah, but remember this will only create one row, if that's what you want...Of course, that will be OK if you want to utilise the "automatic rows" feature
-
You won't regret it ....The Master himself uses it in his blog Same here. No more 'three columns small' stuff for me (no offence to other Grids out there )
-
Absolutely! You can change those. PocketGrid has only two classes; 'block-group' [which creates a row] and 'block' [which creates a column] . Have a look at the css file - it's only 43 lines long unminified ... The b1, etc you see on the demo site are custom classes to make it clearer what's going on. Edit: As you can see, it is very versatile and can be as semantic as you want (if you care about such things ). Btw, block and block-group can be applied to any element, not just <div>
-
Welcome to PW and the forums xporter. Nice to know that our documentation is great! Would Ryan's EventsFieldType be of help? http://mods.pw/5o - Not sure, maybe you'd have to extend it...
-
Using fuel (or another way of setting constants)
kongondo replied to thomas's topic in Module/Plugin Development
init.inc? http://processwire.com/docs/tutorials/how-to-structure-your-template-files/page4 Edit: Oops, maybe not. Read this too quickly. Thought you were referring to template files -
People's choice my friend, people's choice [number of nominations received]
-
Matthew , Isn't it the case that the 3 per category are those that won nominations in their categories? i.e. they've won in the 'primaries' so have already competed against other systems
-
Works fine here (on a PC)....
-
Btw...yes you can; if that module comes with a permission (e.g. Batcher has a permission 'batcher')
-
Thanks Teppo; added to my todo list
-
Guys, apologies for not responding earlier. @Webweaver I've had a thought about the 'summary' text and I want to leave it as is for now. My reckoning is that a summary is just that; a blurb of text (usually one paragraph)... Thanks for reporting the issue with sorting the 'date' field. The Posts Table is being generated from ProcessWire (MarkupAdminDataTable). So, this is not an issue with ProcessBlog per se but thanks for catching that. I have actually been considering using other tables (e.g. DataTable) that are capable of dynamic sorting (i.e. sorting from the database). The sorting your see now is static and does not draw from the database. As for quickpost I have been wavering between making it RTE or not. I reckoned that many people would not be using it often for post creation. If there's sufficient demand I might change it back to RTE. @Pwired Glad you find the module useful. As stated in the first post, I intentionally used lots of template files in an attempt to make it easier for folks to see what's going on in the code. It is definitely not the recommended templating approach. In addition, using the Blog API, the user would be able to use the templating approach they wanted (as well as the CSS framework they wanted). However, documentation to assist users with the API is badly needed (and I am working on this at the moment). So in time, you will be able to 'disable the default front' that comes with MarkupBlog. This means basically deleting the template files . Technically, Blog does not need any of those template files. They are just there to showcase its capabilities. OK, back to writing....
-
I get you now. I'll have a think...Thanks for testing..
-
As for <p></p>, those are added back later. See line 602 of the code if($small) { $out .= "<p>" . $page->summary . "… <a class='more' href='{$page->url}'>" . __('View More') . "</a></p>"; } Hadn't considered images in the summary.... ..Maybe I'll need to add at blog_summary [non-rich text area] to the blog template. Edit Or, for now, maybe not. I don't want to add too many fields...I'll have a think Edit 2: We now have this feature inbuilt in renderPosts(). You can specify tags that should not be stripped as indicated in this post: https://processwire.com/talk/topic/7403-module-blog/?p=78227 (see post_small_allowable_tags)
-
CKEditor: how to adapt config.js and keep it upgradeable
kongondo replied to titanium's topic in Modules/Plugins
Nice! Ryan has added this to the dev branch -
Here are mr-fan's, manfred62's and diogo's cool solutions https://processwire.com/talk/topic/7298-google-custom-search-for-your-browserbookmarks/
-
This needs to go on a tut somewhere then
-
Remember to switch off debug mode before going live (on a remote server). Debug 'true' should never be used on a remote server...for security reasons...
-
Still in Beta but safe to use but I need to add some features before going stable (e.g. scheduled publishing, etc) . Other than that, it works fine...
-
Hi Webweaver, Glad you like the module. It is truncating fine for me here. The code is pulling text to truncate from blog_body. I decided to skip over using a blog_summary since truncation can be done from blog_body. I am guessing it is not truncating because you have not set the second parameter/argument of renderPosts() to true. The default is false (i.e. do not truncate). Apologies for this; I have delayed with documentation but I am currently writing this. Here's example code to make it truncate. $blog = $modules->get("MarkupBlog"); $limit = 10; //limit will be passed to the selector fetching blog posts; //'true' will truncate posts to what we have set in blog_quantity but default to 450 if this is not set $content = $blog->renderPosts("limit={$limit}", true); echo $content;
-
Bwakad, Moved this here (general support forum) from the FAQ from which is for 'Answers to frequently asked questions about ProcessWire.'
-
Hi PWired, I moved this here (off-topic - dev talk) since it is not directly related to ProcessWire