Jump to content

kongondo

PW-Moderators
  • Posts

    7,529
  • Joined

  • Last visited

  • Days Won

    160

Everything posted by kongondo

  1. Yes, you can. Double click on it .
  2. True.. Maybe better to get it like this...(in case down the road someone wonders what the 2 is all about, etc).. $pages($config->adminRootPageID)->httpUrl();
  3. Template caching maybe? Check the Cache tab when editing the relevant template. As for CSS, browser cache? Chrome is notoriously 'cachy!'. You will want to develop with dev inspector open and set not to cache, if that is the case.
  4. Great. Try and re-install Blog and we'll take it from there.
  5. Hi @bot19, Welcome to the forums. The second error is, yes, as a result of trying to install again whilst there are left over components from the first install that failed. I am not sure why the first one failed. I have never seen that error before. As for cleaning up, normally, if the install had worked, you would have a cleanup menu. Since install failed, that cannot help you now. I have an old gist for such eventualities. I believe it should still work. Please use it to cleanup and then try to re-install Blog. If it fails again, we will debug the issue step-by-step.
  6. FYI, Lister (as seen in Find, Templates, etc) in PW admin is Ajax-driven content that utilises pagination.
  7. To the best of my knowledge, there is no module that will make phone numbers on your site clickable. We have a Phone Fieldtype, but I don't think that's what you want.
  8. Sorting the results of a selector Limiting the number of results returned by a selector
  9. Quick answer will be in a template file. I am assuming your next question will be, what is a template file? If I am not wrong, I would encourage you to first read up on ProcessWire, at least get to know the basics. As for a windows server, I have zero experience but IIRC, some people have had success running ProcessWire on such. Welcome to the forums.
  10. @gmazanakis, Is your site a ProcessWire website?
  11. Sorted, then. Excellent. Please amend title of thread to reflect issue has been resolved.
  12. Did you see @Robin S's post above about max_input_vars? Did you try that? Do you have $config->debug set to true for debugging? Error messages? Error message in the dev console?
  13. Update: Multi Sites Sites Manager Version 0.0.3. Multi Sites is dead! Long live Multi Sites!! Happy to announce Beta Release of Sites Manager. Please note, no upgrade path from versions 001 or 002 of Multi Sites. I have updated the first post. Download: GitHub Demo: Remote server single site install (PW 3.x + AdminThemeUIKit). YouTube Documentation: GitHub Changelog Changed name to Sites Manager (formerly Multi Sites). Thanks to @szabesz for suggestion. Fixed bugs in Type or Paste method (key=value pairs must now be separated by new line). Beta release.
  14. For ProcessWire 2.3
  15. Just wondering, since this is a dev site, is it a new site? If yes, was there a reason to install ProcessWire 2.3 or that's how the site was handed over to you? Edit: Welcome to the forums and ProcessWire.. .
  16. Regarding your no URL issue, most like you image field $image is set to hold multiple images (hence returns an array - whether it has only one image or or more). If that's the case, you will need to loop through it.
  17. Thanks for clarifying. I thought you were saying Process module's configs cannot be accessed in the frontend which confused me because I have been able to access a Process module's configs in the frontend as a non-superuser using getModuleConfigData(). , for instance, in Blog's demo template files.
  18. Please clarify this. Were you not able to access configs data of a Process module?
  19. Maybe test for this then? Loosen perms and see if it works?
  20. The following topic is old and some of the stuff is probably out of date but well worth reading.
  21. I think you must have misunderstood the tutorial. The pw-* classes are just placeholder tags that ProcessWire parses at render. They are removed in the final markup. There's a very tiny note about it on that page (I'm not sure why it had to be a note and not just in the text proper ) just above Benefits and drawbacks section.
  22. Try $typoSettingsConfigs = $modules->getModuleConfigData('TypoSettings'); Edit: Oops..just noticed you are in PW3...so, not sure my suggestion would work. Edit 2: Hmm, it should work. OK, I don't know what's going on. I'm having one of those mornings...ignore me, please .
  23. Haven't thoroughly read everything written above. Quick suggestions: $config is your friend For paths, (and other stuff), $config is your friend. Rather than entering paths yourself, let it to the donkey work. For instance, if you have an includes folder in /site/templates/includes/ you can get to that easily using: $path = $config->paths->templates . 'includes/'; Delayed Output If you are not already, I recommend you use this approach. Makes it easy to pass and change variables if needed. See the Automatic Inclusions section (the $config->prependTemplateFile). Your files do not have to be named .inc. They could be .php or even .tpl.
  24. Hmm. Felix is the author and maintainer of the PHP IntelliSense extension I referred to. I do not use the VSC code in-built one. Works for me too in VSC. IntelliSense I have noticed that if I do this: $animals = new Animals(); $traits = $animals->getTraits(); PHP IntelliSense works fine. However, if I do this... public $animals $this->animals = new Animals(); $traits = $this->animals->getTraits(); It doesn't work...I have been meaning to file a 'bug' report. I've tried the other IntelliSense but they don't work as well as Felix's.
  25. Ivan, what exactly? HTML IntelliSense? The extensions I use provide HTML auto-completion, tag matching (and changing) and CSS IntelliSense. I'll post my list of extensions later.
×
×
  • Create New...