I downloaded the script and got some help to fix it because it was all messed up. I have attached a file "ReservationSystem.rar" and it should work out of the box. Also attached the database file "Phpmyreservation.sql".

The thing is the script works great as it is now but when i install a blank version of processwire and import the script to the template folder it wont work. I have tried many things but cant get it to work just error after error etc. Please ask me if you need some more information about this. I know you are the experts so thats why im asking you.

Share this post

Link to post

Share on other sites

Hi, thanks for your reply. I want to have this script under Processwire in the default template map. I am gonna modify the look of it later but for now i just want it to work. I have a website that im working on and this is gonna be a sub page later on. I dont need to have any fields to edit inside admin. Just have it as it is.

Thinking the problem is with some kind of path for it to work, im clueless though.

For me i would go and setup the fields and templates in processwire and just simple use the calendar generation and you could use the HTML, JS and CSS and replace the PHP magic with PW API magic....this yould be much more flexible on the long run.

regards mr-fan

2

Share this post

Link to post

Share on other sites

It got very confusing for me right now I am really bad at php so thats why i need help with this. I dont need any fields/template for the script, dont need to change anything in admin but maybe later though. Have you downloaded the attached files and look at it?

Share this post

Link to post

Share on other sites

As mr-fan suggested, why not just use the great power of processwire? It might take you a few minutes to get the fields/templates set up (though I know you say you dont need it), the advantages I think would greatly outweigh the headache of trying to get this .rar to run reliably on a page that is already in the processwire environment. Using some simple php, a calendar (or even just a check box in the backend etc) you could get this set up quickly.

Share this post

Link to post

Share on other sites

I know very very little about php just a few lines in fact so thats why i need your help. I know design/frontend html css. I need all the functions in the script. But for now i dont need to change any text or anything through admin in this stage. The problem is that the login screen wont show up when i put it inside the template map.

Share this post

Link to post

Share on other sites

I think there is something wrong with the main.js because it wont load the login screen. I have paste the javascript below so if anybody can see whats wrong or maybe not with the script below it would be super.

Share this post

Link to post

Share on other sites

This might have something to do with the fact that ProcessWire by default block access to files in the templates directory. @BitPoet pointed this out here:

On 8/10/2016 at 12:49 PM, BitPoet said:

ProcessWire by default blocks access to files with the extensions php, htm, html, inc and tpl underneath the templates directory (or, to be precise, the shipped .htaccess file does so). This is a security feature.

Thus, to access third party PHP code, you have two choices:

Move the relevant code outside of the templates directory or

create a template with a PHP file in site/templates that includes the external library (in your case instapast-ajax.php, and that's where Ryan's quote comes in) and a page that uses this template (and that provides you with the URL to call from JS)

You might need to move this files etc outside the template directory. However, I have not gone through ALL the code yet as there is a ton. I'll keep digging through it. Someone please correct me if I am wrong, as I have not worked much with assets that dont run through the processwire environment.

Recently Browsing
0 members

Similar Content

Hi, So today I will writing a small tutorial on developing templates in Processwire using Twig Template, Processwire is a highly flexible CMS which gives developers/designers/users options and allows easy extension of the platform. So here goes the tutorial
What is Twig Template ?
Simply put in my own words, Twig is a modern templating engine that compiles down to PHP code, unlike PHP, Twig is clean on the eyes , flexible and also quite *easy* to have dynamic layout site with ease ,without pulling your hair out. Twig is trusted by various platforms. It was created by the guys behind Symfony.
Take this code as an example
{% for user in users %}
<h1>* {{ user }}</h1>
{% endfor %}
This will simply be the equivalent in PHP World
<?php
$userArray = ["Nigeria","Russia"];
foreach($userArray as $user):
?>
<h1><?= $user ?></h1>
<?php
endforeach;
The PHP code though looks simple enough however, you start to notice that you have to be concerned about the PHP tags by ensuring they are closed properly , most times projects gets bigger and comes complex and harder to read/grasp, and also in PHP you can explicitly create variables in the template making it very hard to read as it grows and prone to getting messy WordPress is a major culprit when it comes to that regard.
Have you ever wanted to created separate layouts for different pages and break your sites into different parts e.g Sidebar, Comment Section, Header Section ? the regular approach would be to create individual pages for each section and simply add them as templates for the pages and with time, you can end up having tons of templates, however Twig allows you to easily inherit templates and also override the templates where you can inject content into the block easily. Don't worry if you don't understand the concept, the following parts will explain with an example of how to easily inherit layouts and templates.
Layout
<!DOCTYPE html>
<html lang="en">
<head>
{{include("layout/elements/header.twig")}}
</head>
<body>
<div class="container-fluid" id="minimal">
<header id="pageIntro">
<div class="bio_panel">
<div class="bio_section col-md-6">
<h1>Okeowo Aderemi</h1>
<h2>{{ page.body }}</h2>
</div>
</div>
<div class="clearfix"></div>
</header>
<section id="page-body">
<div class="container">
<div id="intro" class="col-md-7 col-lg-7">
<h1>About me</h1>
<h2>
{{ page.summary }}
</h2>
</div>
{block name="content"}{/block}
<a style="font-size:1.799783em; font-style:italic;color:#d29c23" href="{{pages.get('/notes').url }}">Read more articles</a>
</div>
<div class="clearfix"></div>
</div>
</section>
</div>
<footer>
<div class="header-container headroom headroom--not-top headroom--pinned" id="header-container">
{{include("layout/elements/footer.twig")}}
</div>
</footer>
</body>
</html>
This is basically a layout where we specify blocks and include other templates for the page, don't panic if you don't understand what is going on, I will simply break down the weird part as follows:
Include
This basically is similar to native PHP 'include', as it's name suggests it simply includes the templates and injects the content into the layout , nothing out of the ordinary here if you are already familiar with php's include function.
{{ output }}
This simply evaluates the expression and prints the value, this evaluate expressions, functions that return contents , in my own short words it's basically the same as <?= output ?> except for the fact that it's cleaner to read.
{% expression %}
unlike the previous this executes statements such as for loops and other Twig statements.
{% for characters in attack_on_titans %}
<h1> {{characters}} </h1>
{% endfor %}
This executes a for loop and within the for loop, it creates a context to which variables in that context can be referenced and evaluated, unlike dealing with the opening and closing PHP tags, Twig simply blends in with markup and makes it really quick to read.
I will simply post the contents of both the header and footer so you can see the content of what is included in the layout
header.php
<meta charset="utf-8"/>
<meta content="IE=edge" http-equiv="X-UA-Compatible"/>
<meta content="width=device-width, initial-scale=1" name="viewport"/>
<title>
{{ page.title }}
</title>
<link href=" {{config.urls.templates }}assets/css/bootstrap.min.css" rel="stylesheet"/>
<link href="{{config.urls.templates }}assets/css/main.min.css" rel="stylesheet"/>
<link rel='stylesheet' type='text/css' href='{{config.urls.FieldtypeComments}}comments.css' />
<link rel="stylesheet" href="{{config.urls.siteModules}}InputfieldCKEditor/plugins/codesnippet/lib/highlight/styles/vs.css">
<script type="text/javascript" src="{{config.urls.siteModules}}InputfieldCKEditor/plugins/codesnippet/lib/highlight/highlight.pack.js"></script>
<script src="{{config.urls.templates }}assets/js/vendors/jquery-1.11.3.min.js">
</script>
<script src="{{config.urls.templates }}assets/js/vendors/bootstrap.min.js">
</script>
<script src="{{config.urls.FieldtypeComments}}comments.js"></script>
<link rel="stylesheet" type='text/css' href="{{config.urls.templates}}js/jquery.fancybox.min.css">
<script src="{{config.urls.templates}}js/jquery.fancybox.min.js"></script>
{block name="javascriptcodes"}{/block}
footer.php
<nav class="site-nav pull-right">
<div class="trigger">
<a class="page-link" href="{{pages.get('/about').url}}">
<span>{</span> About
<span>}</span>
</a>
<a class="page-link" href="{{pages.get('/notes').url}}">
<span>{</span> Journals
<span>}</span>
</a>
<a class="page-link" target="_blank" href="https://ng.linkedin.com/in/okeowo-aderemi-82b75730">
<span>{</span> Linkedin
<span>}</span>
</a>
<a class="twitter page-link" target="_blank" href="https://twitter.com/qtguru">
<span>{</span> Twitter
<span>}</span>
</a>
</div>
</nav>
There's nothing special here, other than twig simply injecting these fragments into the main layout , the next part is the most interesting and important concept and benefit that Twig has to offer
{% block content %}{% endblock %}
This tag simply creates a placeholder in which the content would be provided by the template inheriting this layout, in lay terms it simply means child templates will provide content for that block, the 'content' simply uses the name 'content' to refer to that specific block, so assuming we were to inherit this template it would simply look like this.
Inheriting Template Layout
{% extends 'layout/blog.twig' %}
{% block content %}
<div class="container blog-container">
<section class="blog">
<header class="blog-header">
<h1>
{{page.title}}
</h1>
<h5 class="blog_date">
{{page.published|date("F d, Y")}}
</h5>
<br>
</br>
</header>
<div class="blog_content">
<hr class="small" />
{{page.body}}
<hr class="small" />
</div>
</section>
</div>
{% endblock %}
{% block nav %}
<div class="col-md-4 col-xs-4 col-sm-4 prev-nav">
<a href="{{page.prev.url}}">
← Prev
</a>
</div>
<div class="col-md-4 col-xs-4 col-sm-4 home-nav">
<a href="{{homepage.url}}">
Home
</a>
</div>
<div class="col-md-4 col-xs-4 col-sm-4 next-nav">
<a href="{{page.next.url}}">
Next →
</a>
</div>
{% endblock %}
In this snippet you can easily notice how each blocks previously created in the header and layout are simply referenced by their names, by now you will notice that twig doesn't care how you arrange the order of each block, all Twig does is to get the contents for each blocks in the child templates and inject them in the layout theme, this allows flexible templating and also extending other layouts with ease.
Twig in Processwire
Thanks to @Wanze we have a Twig Module for Processwire and it's currently what i use to build PW solutions to clients
https://modules.processwire.com/modules/template-engine-twig/
The Modules makes it easy to not only use Twig in PW but also specify folders to which it reads the twig templates, and also injects Processwire objects into it, which is why i can easily make reference to the Pages object, another useful feature in this module is that you can use your existing template files to serve as the data provider which will supply the data to be used for twig template.
take for example, assuming I wanted the homepage to display the top six blog posts on it, TemplateEngineTwig will simply load the home.php ( Depending on what you set as the template), it is also important that your twig file bears the same name as your template name e.g home.php will render into home.tpl here is an example to further explain my point.
home.php
<?php
//Get the Top 6 Blog Posts
$found=$pages->find("limit=6,include=hidden,template=blog-post,sort=-blog_date");
$view->set("posts",$found);
The $view variable is the TemplateEngine which in this case would be Twig, the set method simply creates a variables posts which holds the data of the blog posts, the method allows our template 'blog.twig' to simply reference the 'posts' variable in Twig Context. Here is the content of the 'blog.twig' template
blog.tpl
{% extends 'layout/blog.twig' %}
{% block content %}
<div class="block_articles col-md-5 col-lg-5">
{% for post in posts %}
<div class="article_listing">
<span class="article_date"> {{post.published}}</span>
<h2 class="article_title">
<a href="{{post.url}}">{{post.title}}</a>
</h2>
</div>
{% endfor %}
{% endblock %}
So home.php sets the data to be used in home.tpl once Twig processes the templates and generates the output, twig takes the output from the block and injects it in the appriopriate block in the layout, this makes Processwire templating more flexible and fun to work with.
The major advantage this has; is that you can easily inherit layouts and provide contents for them with ease, without the need of running into confusions when handling complex layout issues,an example could be providing an administrator dashboard for users on the template side without allowing users into the Processwire back-end. You can also come up with several layouts and reusable templates.

Feel free to ask questions and any concerns in this approach or any errors I might have made or overlooked.
Thanks

I have a file I want to access with ajax:
The purpose of this file is to iterate through a repeater, and get the image from each entry.
The number of images in the image field is set to 1, and just for good measure, to return a single image.
And my code:
// site/ajax/processImage.ajax.php?group=1206
require_once($_SERVER['DOCUMENT_ROOT'].'/index.php');
$resourceGroup = (int) $_REQUEST['group'];
// get the Repeater field
$resources = $pages->get($resourceGroup)->resources;
foreach ($resources as $resource) {
echo $resource->title;
// Works as expected
echo $resource->image->url;
// /site/assets/files/1259/
echo $resource->image;
// filename.jpg
echo $resource->image->description;
// nothing
}
See comments above for what is output, why isn't URL giving me a full URL, and no description is available?
If I try to access $image->size() I get the following fatal error:
Error: Uncaught exception 'ProcessWire\WireException' with message 'Method Pageimages::size does not exist or is not callable in this context' in F:\sites\<sitename>\wire\core\Wire.php:519

Hey there,
i have a big Problem. I migrate Processwire with a Plugin from my local Mama Server to a 1&1 web server. After few Problems with Internal Error (.htaccess), the site looks greta and its work. But my Admin Panel are not working correctly. Before I installed the AdminThemeUIKit but now I can't install ist anymore and I can't refresh my modules. Nothing happens after a mouse click on it. If I am going to the pages, I can't see anything. There isn't a Site Tree or anything else. I can not change anything there. Please help me, it is a huge Problem for me... The admin looks like the very beginning of Processwire !!!