Recently Browsing 0 members
No registered users viewing this page.
I need to import regularly - every 15 or 30 days - a big .xslx file into my PW installation.
This file now has 14 columns, 5.000 rows and grows every month.
I'll need to group, order and work with these data to:
analyse User monthly costs analyse User costs per Asset ... User (real AD account) has to match with a PW user - I can't join to the domain - but as you can see I have some services users (start with sca_*) or no user at all. Those rows have to be assigned to a specific user, e.g. account100.
I would like to be able to have a kind of diff function to compare User assets between this and last month (and so on) other request is to have a notification when something change for a User between actual and latest import First request: which is the best solution to store those data in your opinion? Page, Table, Repeater Matrix, ...?
Those are very repetitive data and I think a page reference is better than to import all the data every time but I have to understand how to manage those "dynamic" groups of software (AccType Det), hardware (Asset), ... For example Price will be imported and not stored with the description because it could be change in the future and I'll not have any control on it.
User,OE,productNmr,AccType1,AccType Det,Count,Price (€),Sum,ASNA,CC,AccType Info,Asset,AccGroup,,,,,,,,,,,,,
I'm combining two PW sites into one, Site A into Site B.
At each step, I did it bit by bit as the 'all at once' approach failed.
First, I exported all the fields from Site A and imported into Site B. Any field types not supported by import/export, eg FieldtypeOptions I manually recreated. All good.
Next I exported all the templates from Site A and imported them into Site B and copied across their associated template files. All good.
Finally I exported the pages I needed from Site A into Site B - again, bit by bit to ensure it all went smoothly.
From the admin side, it all looked and worked perfectly.
Front end was a totally different story. All existing pages in Site B worked as expected. NONE of the pages imported from Site A displayed. They all ended in a redirect loop with no errors in the PW logs or Tracy Debugger.
After some trial-and-error, I finally got it working with:
- create a new template in Site B admin with no associated template file and just a title field
- import the fields from the imported Site A template into the newly created template (both on Site B)
- copy the Site A php template file into a new file that matched the new PW Site B template name and save in Site B site/templates
I can deal with the above workaround. Just curious to know if I did something wrong or if the template import/export feature is problematic?
While the export/import was a slow process, turned out the front end redirecting issue was unrelated. For reasons unknown, all templates marked as HTTPS only were the ones redirecting, ie all templates from Site A. Finally solved it by changing the $config->https to true in site/config.php
Now the pages display correctly as https whether the template forces the issue or not.
i am receiving and error whenever I try to run my processwire on localhost,
-- -- Table structure for table `field_fieldset_meta_end` -- CREATE TABLE `field_fieldset_meta_end` ( `pages_id` int(10) UNSIGNED NOT NULL, `data` int(11) NOT NULL ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `field_fieldset_meta_END` -- CREATE TABLE `field_fieldset_meta_END` ( `pages_id` int(10) UNSIGNED NOT NULL, `data` int(11) NOT NULL ) ENGINE=MyISAM DEFAULT CHARSET=utf8; anyone ?
whenever I make a new database and upload it there, database get imported without errors.