kongondo

Get ready for a face palm ? On line # 145 public function __processInput(WireInputData $input) { the method processInput() is missing one underscore at the beginning and should be public function ___processInput(WireInputData $input) {

Great catch. Existing modules better watch out then.

That's crazy! Wild guess: does giving them custom names or IDs change anything?

So potentially affecting any (process?) module that renders two button inputfields in a single form?

Hi @psy. Please request @apeisa to give you access. He has the 'keys' :-).

...from the link provided above ?. So, yes, it is like NB Navigator. The advantage is that Visual Studio Code is our editor of choice for various reasons ? (now, I hope this does not lead to a NB vs VSC debate; that really is not the purpose of this thread).

Yes, you are right, my apologies! I forgot about that one ?

Currently, you can only do it using the API (hooking), not the GUI. See custom price here: https://www.padloper.pw/documentation/custom-pricing-for-product/ Edit: See correction in next post. There is a basic discount codes module ?

Hi @zoeck, Thanks for your interest in Media Manager. I can't give a definite date but it will be in the autumn.

Thanks Adrian. This got me more curious because I vaguely remember having a talk about lower case vs upper case. So, I went back and checked, all the way from 2.2 up to and including 2.7.3. It was only lower case in those versions. So, this must be a 3.x introduction.

@Karinne Cyphers, Thanks for the screenshots. They've helped clarify issues. I suspected as much given the error MySQL was throwing. The error itself is originating from ProcessPageLister (a core module) which Media Manager extends and uses to fetch and display media pages. As far as I can remember, ProcessWire only allows lower case letters for field names. Going by your screenshot though, it seems this changed sometime back. Back to your issue, the error is a ProcessWire error and not Media Manager's. I'm not sure whether it should be filed as a ProcessWire bug (specific to your server environment, maybe) since it now seems upper case letters are allowed in field names. I'll try and find out.

Hi @Karinne Cyphers, I don't remember ever seeing this error in respect of Media Manager. A couple of questions: Do other fields, either in the same template or a different one work OK? For instance, text fields, etc Is the problem with this one template or have you tried a different template? Maybe there is an issue with the name of your field. Try renaming it to something else and use lower case letters only MySQL and PHP versions? If possible, please post a screenshot or animated gif of the error, thanks.

$roles->find('');// all roles //$roles->find($selector);// if want particular roles http://processwire.com/api/ref/roles/ Adapt as required for module use

Yes, they would be overwritten. I agree, however, the current Blog API documentation is sufficient to get you started, I would think ?. True, but it shouldn't be a problem because the most important thing for you is to use Blog's own methods. E.g. renderPosts(), renderCategories(), etc. They'll still work irrespective of output method. Hence, the reason I pointed you to the examples in the demo template files. Maybe if you could explain what exactly you need help with?

You can also do a check using the template 'menus'. That's the template used by menu builder menus.

Hi @MilenKo, Your code was close. If a menu is not found AND the user is a supersuser, Menu Builder will throw a WireException. If the user is not a supersuser, it will return false (boolean). In such a case, you can do your check like this: $mb = $modules->get('MarkupMenuBuilder'); $out = $mb->render(1234, $options); if($out) echo $out; // OR //if($mb->render(1234, $options)) echo $mb->render(1234, $options);

Thanks for the explanation! ?

Not unless you roll back to previous versions or modify the module itself to your liking (being aware that any future updates will wipe out your changes unless you rename your module class and files). Welcome to the forums @Ben Sayers. Yes, apologies for the documentation. Despite my best intentions, I've never been able to find time to complete it. Again, sorry about this. Docs should be clearer. Not at the moment, I'm afraid. Any reason why you can't/won't use the Blog module itself to render your posts? The demo template files and the present documentation provide examples that should get you going.

Hi @pwfans, Welcome to the forums. I'm glad you are finding the module useful. Could you please provide more information regarding this approach? I'm sure it would come handy to others using to look this module. For instance, what template are you referring to? A template file? Also, the bit about the <form> and the textarea is not clear. Thanks!

Excellent idea! I'll add it in the next version of MM. Meanwhile, for now, you can edit the file MediaManagerRender.php and enter the following code after the Filename, i.e. on line #676: '<span>' . $this->_('URL') . ':</span> ' . $m->httpUrl . '<br>' . Please note, the output (URL) might be quite long, so the CSS could be off. However, I cannot work on this now since the new version of MM will have a different layout. It will present a challenge though since the descriptions, etc are viewable on hover. When the house is moved away, the overlay goes. This means, it will not be possible to copy the URL. I hope this makes sense. I will have to think more about this.

Hmm. That's not ideal. This is not how MM usually works ?. What's your server environment? ProcessWire version? I have never used the Redirect module. Could you please show me a screenshot of the input where the URL is supposed to go? Do you need the URL or the path?

@Thomas Scholz, Welcome to the forums. Thanks for the purchase. Media are saved as pages, hidden away under Admin. It seems a situation occurred whereby the creation of a media page did not complete and subsequently, the media was re-uploaded and the module tried to create the page again. Since in PW, no pages under the same parent cannot share a name, you get the violation constraint. Was this a media with a big image you were trying to upload? Try deleting the page physically in your page tree: admin > media-manager > media-manager-image > heikohotel-hotel-am-stadtpark-buffet-2-9840a-1032. Make sure to delete it and also empty the trash. If not, you might have to physically delete the page entry in your DB. This situation has happened to me once or twice in the past. I know it is annoying, apologies. On a related note, Media Manager has a setting for handling duplicate media. I'm not sure why that did not kick in before your situation occurred. Most likely, like I said, a page creation did not complete. Let me know if you are still not able to resolve this and I can have a look if the site is online. I am not sure I understand this. Do you mean, they want to link to media, for example, within text in CKEditor (either as an image or link)? If the answer is yes, just click on the image or link icons in CKEditor and you will see links to pick the media from Media Manager.

Yes, but only via the normal PW page tree. Posts are just PW pages that use the template blog-post. I don't know what Blog style you used, but just add a child page to whoever the parent of pages using blog-post is. If using style 1 of Blog, then the parent should be the page Posts and it uses the template blog-posts. Adding a child to that parent page should automatically select the template blog-post for the children being added (i.e. individual posts).

Sorry, @St3f4n. I forgot to answer your question! Use post_large_image option for featured image in a non-summarised (i.e. large/full) post and post_small_image option for featured image in a small/summarised post (e.g. in the default blog-category template file). Does this help? Welcome to the forums ?.

Currently, such 'user-added' fields are not supported in Quick Post. They can only be accessed when you edit the blog page normally. Maybe it's something I need to think about.