-
Recently Browsing 0 members
No registered users viewing this page.
-
Similar Content
-
By louisstephens
So I was going to build a todo tracking app for myself to test/broaden my knowledge of processwire, and so far it has been taxing 😓. My Site structure is:
- Project One - Phase One - Task - Task - Task - Phase Two - Task - Task - Task So far it was pretty easy, I can easily foreach through the Project and get the phases with their tasks. However, it gets a bit muddled when I have more than one project as I was trying to have a dashboard where the content switches out to the selected project as opposed to accessing each project via their own url. How would yall handle this?
My next hurdle is each task has a select field (for project status) that I want to update via ajax (for the smooth transitioning).
Scenario: You finish a task, change the option from "new" to "completed", and an onclick changes the status drop down background to green (which I have working), but then posts/saves a field on the backend to the new option.
I have a page called "Actions" set up with url segments using
if ($config->ajax && $input->urlSegment1 == 'change-status') { //save update field on admin } However, I am a little fuzzy on how to actually pass the current page along with the new selected status to actually update the page (task). I guess I am not very far into my endeavor. Any help would be greatly appreciated.
-
By louisstephens
So this is more or less just a question regarding best practices, and how to actually achieve this. I have an internal tool I built awhile ago that has just gotten very "trashed". The naming conventions are all out of whack due to trying to get something completed, and pages are just everywhere. The fields got really out of hand as well, but I believe I have found a much cleaner field structure with the Repeater Matrix and a few other ProFields. I decided recently to rewrite the template structure and the fields from scratch to keep everything nice and neat, but then it hit me that I would need to move all the previous data over and populate the new fields etc.
The current tree looks something like:
Group Title - Section A (template "section") - Category One (template "category") - Category Two (template "category") - Section B (template "section") - Category One (template "category") - Category Two (template "category") Etc etc... The structure is pretty good, and I am thinking of keeping it as it serves my purpose. However, I now have about 140 Sections with child pages that I would hopefully like to move to different templates, as well as changing the child templates/mapping data to the new fields. The only fields I need to worry about are a few textareas, text fields, options field, as well as 1 image filed.
I guess my real question is, what is the best way to go about this "migration" via the api while keeping the parent/child structure. It would be ok to leave it as is and chip away at it if I were the only one using it, but unfortunately that is not the case.
I guess one approach would be to copy over the entire structure and make the move to the new templates/fields. Once we have verified all the data/templates are correct, we could remove the old structure and possibly rename the new to mirror the old. However, this might just be too complicated.
-
By EyeDentify
Hello Fellow PW Fans and Gurus.
I have run into a problem where i have created a template without a template file associated with it.
Now i would like to HAVE a template file associated with it, not an alternate but as the main template file.
So i thought, that's easy, I upload the template file and change it in template settings but I only get the Alternate template file setting?
Ok so maybe i can change it via the API , so i wrote some code for this.
<?PHP function changeTemplate($pages = null, $templates = null) { /* get the pages to change template on */ $logItems = $pages->findMany('template=tmp_log_item'); /* get the template object for our desired template */ $Template = $templates->get('tmp_new_log_item'); foreach($logItems AS $key => $logData) { /* use template object $Template to set template */ $logData->template = $Template; /* save page item */ $logData->save(); } } /* do the magic change */ changeTemplate(); ?> Needless to say, PW was not happy about this, It throw up an error message:
Error: Exception: Invalid value sent to Page::setTemplate (in /home/virtual/mydomain/public_html/wire/core/Page.php line 1782)
Now from what i understand i gave $logData->template the wrong type of value.
So what should the value be to correct this?
When I read the docs at: https://processwire.com/api/ref/page/
the value can be "string" or "Template".
So i gave it a string and it went haywire.
How should I approach this cause I realy dont want to manually change template file on över 50 plus pages
Maybe I should use the Template class to create the value that the API wanted, but I am unsure how to use it.
Thank you for any info you can give me on this.
If you want more info to help me, ask and I will try my best to give it to you.
Updated and Solved
I solved the problem and have updated the code to reflect this.
Essentialy i used the get() method of $templates to get the template object for my template i wanted to use using the template name.
I gave the Object to the $logData->template property and all went well.
We learn something new every day.
One Note:
The template file you want to use must have been uploaded and added as a template in the Template section in the Admin for this code to work as expected.
-
By chcs
After running this code in my module's __install() the template_id is not set. Any ideas why? (The export contents from the template created and the one that I built with Admin are the same. Both exports have the template_id is set to mm_state. When I go to edit the field in Admin, the template is not showing on the Input tab and it doesn't show the template title on a page using the template that uses this field. Using processwire 3.0.98)
// mm_state
$field = $this->fields->get('mm_state');
if (!@$field->id) $field = new Field();
$field->type = $this->modules->get("FieldtypePage");
$field->name = 'mm_state';
$field->label = 'State';
$field->derefAsPage = 2;
$field->inputfield = "InputfieldSelect";
$this->fields->save($field);
$field->labelFieldName = 'title';
$field->template_id = 'mm_state';
$field->columnWidth = 100;
$field->required = true;
$this->fields->save($field);
-
By DamegoGmbH
Hi there,
we are a small Communication Agency in Munich and we are searching for a Processwire Developer.
A lot of our Online Projects are based on Processwire and our current Developer is switching from Freelance to a full term job.
The work can be done remotely from anywhere.
For more Informations please contact me directly via Email: p.kirschvink@damego.de
Looking forward to hear from you.
Best
Paul
-
