• Content count

  • Joined

  • Last visited

  • Days Won


kongondo last won the day on February 16

kongondo had the most liked content!

Community Reputation

4,738 Excellent

About kongondo

  • Rank
    Hero Member
  • Birthday

Profile Information

  • Gender
    Not Telling
  • Location

Recent Profile Visitors

22,177 profile views
  1. Which module is this?
  2. @cosmicsafari. Welcome to the forums and ProcessWire. You will need to include your Foo.php file in your module ( MyModule.module). ProcessWire doesn't know about it and will not include it for you. You can require it outside the class or in its __construct() or function init() methods (I think either of the three should work). $dir = dirname(__FILE__); require_once($dir . "/Foo.php"); Maybe it was just a typo, but module files end in .module (that's the extension, not .php)
  3. Preview of new Blog Dashboard UI coming in the next update... Posts List Quick Post (now in modal) Thoughts? Opposition ?
  4. Maybe this is the issue?
  5. Is that a "Yes, problem solved!" or a "Yes, I've ticked all the boxes but it still doesn't work!" ?
  6. The method rendering those side menus is renderNav(). It takes as a second parameter an array or PageArray. In blog.post (the template file for a single post, which you wish to edit), around lines 20 - 22, you can see it takes the PageArray made up of the current post's categories (blog_categories) as follows: if(count($page->blog_categories)) $subNav .= $blog->renderNav(__('Related Categories'), $page->blog_categories); In the main blog page, i.e. the one that uses the template blog.php, around lines 14 - 15, we see the same function taking a different PageArray; one that is made up of ALL the categories as follows: $categories = $pages->get('template=blog-categories');// this grabs the parent of all category pages $subNav = $blog->renderNav($categories->title, $categories->children);// we pass its children, a PageArray made up of all categories So, the latter code (the lines 14 - 15 in blog.php) is what you need to copy to your blog-post.php to achieve your desired result. Please note that in that demo code, there is no limit set to the number of categories that are returned. If you have lot's of categories you will want to place a limit on the children, e.g. $categories->children('limit=50');
  7. There is (ahem..) a commercial module for this kind of thing. It's called Media Manager (Disclosure: I am its author ) By the way, I don't think your post matches the content of this thread. It would be best if you started a different topic. We would then transfer your post and its responses to your new thread. Alternatively, if you can suggest a title for your new thread, we can hive off these posts into that new topic directly.
  8. That's the expected behaviour. When you click on a category, you are taken to its page and are shown a list of all the posts that use that category, i.e. /category/my-category/. I can't remember how you set up, but if your "news" is a category, clicking on a post categorised under "news" should take you to /category/news/ with a list of all posts classified as news items. Seems something changed in your system? Some autoload module that is affecting save? I have tested and it works fine here. Does the same thing happen if you edit the post page normally? (i.e. not in the Dashboard modal).
  9. @Standard Forge, Glad you find the module useful . As you point out, that's a bad idea . For complex or custom menus, there's a better way to achieve the result you want. I decided not to add any more features such as these to MenuBuilder (including "Bootstrap does this or that"...sort of requests). Instead, since a while back, Menu Builder now provides an API that will return your menu items allowing you greater control over their output. This is done via the method getMenuItems(). Please find detailed examples in this post. Grab one and edit it to suit your needs. Let us know how you get along.
  10. Not a good idea though without limits...can easily overwhelm the server if lots of descendants: return $page->find('');// will find all descendants
  11. I am thinking of changing the way variations + attributes are created and applied. Currently, these have to be typed whenever one needs them. For different products that share an attribute (e.g. 'Red') but not necessarily a variation configuration, all that typing is repetitive. For instance, the colour Red means the same thing irrespective of whether it is a Car or a T-Shirt or a Phone. If you have all these products for sale, you should be able to just select colour from some list you previously typed and be presented with all colours from which you can select which apply to your product. Meaning, at the product/page configuration level, you will first have to select the variations you want, e.g. Size, Colour, Material, etc....then select the respective values/attributes, e.g. Yellow, etc. Small, etc.
  12. Hmm. That's an interesting observation. I am curios that no one else (as far as I can tell) has had/reported a similar experience. I wonder if it has to do with your setup?
  13. Yes, that's CSS issue. Try and see if it works . Are you using the demo template files that come with blog or did you create/or are using a blank blog-post.php? If the latter, then please have a look at the example demo file. It is a bit redundant to have the code you pasted (which is an example code I gave for some other context) within a blog-post page itself (i.e. redundant to use it in blog-post.php which is the template file for a single blog post).
  14. Hi @suntrop, I know you told me that you'd already found a solution for your project. If you have the time though, I'd appreciate any thoughts you have about this new module (offering variations and attributes functionality) that I am developing. Thanks.
  15. @Jeff C, Welcome to the forums and ProcessWire . The usual way is to use page fields (page reference fields). Please see this content: