Jump to content

Search the Community

Showing results for tags 'paths'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • Login Register Pro
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 5 results

  1. Have read loads of similar threads but can't find the deifnitive answer. I'm bootstrapping ProcessWire into a Magento installation. Everything is working fine in terms of expected PW API functionality, however I cannot get the paths for images in the site work correctly. ProcessWire is installed in a subfolder called 'pw'. If I load the PW site directly e.g. visit mainsite.com/pw everything loads fine and all image paths are correct. If I load the parent site in the root folder with the PW bootstrapped page content rendered within it, the image paths don't contain the subfolder and so are broken. So I get https://mainsiteexample.com/site/templates/img/test.jpg instead of https://mainsiteexample.com/pw/site/templates/img/test.jpg I've tried updating the rewrite base in the .htaccess file but it doesn't seem to make any difference. Have also tried various settings in the config file to no avail. Wondering if rewrite base perhaps isn't working as intended because I'm behind a NGINX/Apache hybrid environment?
  2. I'm trying to make an AJAX call from within a template to a php script within my templates folder, but I'm getting a 404 from all URLs. Is there a proper way to directly address scripts within PW templates? I've read it will work in the site root, but I'd rather keep all the code together if possible.
  3. Short explanation Is it possible to hide a page from front-end output but keep the ability display it's children? Ideally I'm looking for a solution that doesn't involve htaccess or nginx So lets say I have a breadcrumb trail of: Home > News > Posts > news story 1 and I want to mask off the folder called Posts so it becomes just Home > News > news story 1 I still want to retrieve the child pages of Posts using selectors etc. Long explanation I'll give you a use case... I start off with a News section and its children are news stories. News (name=news, template=news-container) - news post 1 ( template=news-item) - news post 2 ( template=news-item) - news post 3 ( template=news-item) - news post 4 ( template=news-item) The structure above lets me use the Add New function because the Parent and Children both have very specific templates and settings. Client then tells me that there are News child pages which are not news items. Lets say they want to add pages called Public Relations Contacts, Media Enquiries and Events They need to be child pages of News but they can't go in the root. They don't need a news-item template and I don't want them to be pulled into any selectors targeting template=news-item or parent=/news/ etc What I usually end up doing is putting all the news items inside a hidden folder called Posts and redefining the Family settings to retain the Add New functionality News (name=news, template=news) - PR Contacts - Media Enquiries - Events - Posts (name=posts, template=news-container) - - news post 1 ( template=news-item) - - news post 2 ( template=news-item) - - news post 3 ( template=news-item) - - news post 4 ( template=news-item) The problem is that my breadcrumb trail looks like this Home > News > Posts > news story 1 Although it's logical and structurally sound, there's a duplicate there in terms of content. Both News and Posts pages display a list of News items. I'm probably not describing this very well but maybe you have the same issue and have a solution?
  4. I'm having some problems with css, include and image paths and wondered what the advice was for the location of following assets (folder in root) - scripts - images - css Currently I have it in the root but perhaps it should be located in the default site/assets/ directory which comes with PW? Reason I ask is because I have a templates folder with a homepage and basic-page template located at site/templates. Both files are located in exactly the same level but both require different paths for the CSS Homepage only works with <link rel="stylesheet" href="assets/scripts/foundation/css/normalize.css"> <link rel="stylesheet" href="assets/scripts/foundation/css/foundation.css"> <link rel="stylesheet" href="assets/scripts/foundation/css/foundation-custom.css"> <link rel="stylesheet" href="assets/css/styles.css"> Basic page only works if I add "../" before above <link rel="stylesheet" href="../assets/scripts/foundation/css/normalize.css"> <link rel="stylesheet" href="../assets/scripts/foundation/css/foundation.css"> <link rel="stylesheet" href="../assets/scripts/foundation/css/foundation-custom.css"> <link rel="stylesheet" href="../assets/css/styles.css"> I should probably make the above into a single include but I'd rather solve this mystery first.
  5. Hope this is the right place for this. Following scenario: PW is running on my localhost: http://localhost/mysite when I insert an image into the textarea the path is like this: "/mysite/site/assets/files/1028/berlin.jpg" Then I changed to a development host name, which point to the same directory: http://mysite.dev Then all the inserted images do no work anymore, because obviously "/mysite/site/assets/" does not exists, it then should be "/site/assets/" Since the image path is written in this plain form into the db, this kind of inflexible. Any solution to this? Edit: It sure could be done easily with a .htacces rewrite: RewriteRule ^mysite/(.*) $1 but I'd consider this hacky then.
  • Create New...