Jump to content

kongondo

PW-Moderators
  • Posts

    7,479
  • Joined

  • Last visited

  • Days Won

    146

Everything posted by kongondo

  1. 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
  2. People's choice my friend, people's choice [number of nominations received]
  3. 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
  4. Works fine here (on a PC)....
  5. Btw...yes you can; if that module comes with a permission (e.g. Batcher has a permission 'batcher')
  6. Thanks Teppo; added to my todo list
  7. 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....
  8. I get you now. I'll have a think...Thanks for testing..
  9. 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)
  10. Here are mr-fan's, manfred62's and diogo's cool solutions https://processwire.com/talk/topic/7298-google-custom-search-for-your-browserbookmarks/
  11. This needs to go on a tut somewhere then
  12. 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...
  13. 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...
  14. 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;
  15. Bwakad, Moved this here (general support forum) from the FAQ from which is for 'Answers to frequently asked questions about ProcessWire.'
  16. Good to know. I have marked Nico's post as the best answer given his solution worked for you. Btw, I am curious why you were getting 404s as opposed to 403s?
  17. Hi PWired, I moved this here (off-topic - dev talk) since it is not directly related to ProcessWire
  18. Titanium, mind creating a feature request to Ryan on GitHub? Thanks.
  19. See some other options by Ryan here: https://processwire.com/talk/topic/407-processing-contact-forms/?p=3106
  20. OK, let's hear what the experts say ....I agree it would be nice to have a custom config.js
  21. Custom configurations are now in /site/modules/InputfieldCKEditor/. I am guessing you know that now CKEditor is the default editor in PW (see dev branch) I am guessing but not sure that you could also add your custom config.js to that directory instead? Have a read here: http://www.flamingruby.com/blog/processwire-weekly-13/ [see Upgrades to CKEditor] https://github.com/ryancramerdesign/ProcessWire/tree/dev/site-default/modules/InputfieldCKEditor
  22. Update: Minor version bump to 1.2.1 after some minor styling issues updates. Documentation: I am taking a short break from writing code to write some badly needed documentation for Blog (and some other PW tutorials if I get time ). I am writing this documentation as tutorials which I will post on my website soon. I'll keep you updated. I haven't forgotten any Blog features pending requests
  23. Hi all, Here's a preview of a Gallery photo album module I am working on (very slowly! ). Development is currently in closed beta testing. The module will consist of a backend (as seen on video below) and a frontend that is framework and lightbox agnostic, aka plugin whatever and it will still work. Features Unlimited number of albums and sub-albums (easy to query using PW API) Multiple methods to add albums and photos (including uploading images and zip files, scanning a folder for FTP'ed photos, etc) Automatic album and photo creation based on names of folders and files respectively Bulk editing (moving, deleting, tagging, etc) Manager themes in several colours A bit of eye candy Etc... This is in beta so it is still rough around the edges. Feature suggestions? Yes please Apologies the video is way too long and you might get bored toward the end...
  24. Manlio, I may not be able to give you specifics but here's a couple of things... Registration You say this but then add this I am a bit confused. To clarify, you mean that you will not be registering NEW users because you already have users, right? Users What format is your table in? CSV, SQL? Importing is not difficult but we need to know the format they are in. Yes, extending the users template is easy and is normally the way to go. There's various examples on the forums. If you need more help here just ask. Importing passwords can be tricky though. No need to create users again. Just use PW inbuilt users (which, behind the scenes, are actually pages themselves! ; Don't let this confuse you. Think of pages as data storage containers [of course the data is in the fields themselves]) Courses One thing you need to clarify is how you want the site to function. I guess here you are really talking about categorising your content. Have you seen this tutorial I did about categorising content? If not, have a look and see where your use case fits in. Then, you can come back and structure your site in the most suitable fashion. We appreciate all the help we can get. Yes, tutorials are not that many but as you have probably noticed, we are working on it. My advice for your task at hand. Divide up the task and tackle one issue at a time (but of course, you need to have a clear picture of where you are going first, otherwise you might be going round in circles). Try things and ask specific questions (once you've searched and not found an answer is preferable ) but feel free to ask please.
×
×
  • Create New...