I created a simple blank install profile for ProcessWire. I think it has been asked for a couple times, although the basic site is something really good to start with and fast to get rid of things you don't need. However in case someone wants one here it is.
https://github.com/s...ireBlankInstall
PROCESSWIRE 2.+ BLANK INSTALL
==============================
This is a blank site profile for ProcessWire2+. It's done using the ProcessExportProfile module.
There's only the following left in this profile:
Fields:
- title
- body
ProcessWire Templates
- home
- basic-page
Template Files
- admin.php (required)
- home.php (required root page)
- basic-page.php (404 page)
INSTALLATION
=============================
Get the latest ProcessWire install package. Before you install, replace the folders
/basic-site/install
/basic-site/templates
with the ones from this blank install.
Proceed with the installation as usual.
Profile: Blank Install Package
Started by Soma, Apr 11 2012 02:35 AM
16 replies to this topic
#1
Soma
-
- Moderators
-
- 3,187 posts
-
1744
Hero Member
- LocationSH, Switzerland
Posted 11 April 2012 - 02:35 AM
@somartist | modules created | support me, flattr my work flattr.com
#2
netcarver
-
- Members
-
- 428 posts
-
341
Sr. Member
- LocationUK
Posted 11 April 2012 - 06:11 AM
Nice work Soma.
Just thinking aloud for a moment but if simplicity of installation is the goal of this, then perhaps it would be better to do a downstream distribution of ProcessWire; something like "ProcessWire-Clean"?? Not sure of the best way to do this but one approach might be to just maintain a fork of the main PW repo with all these changes applied. If Ryan were to link to it from the main site then folks would have the option of getting PW+demo site or the clean install.
Just thinking aloud for a moment but if simplicity of installation is the goal of this, then perhaps it would be better to do a downstream distribution of ProcessWire; something like "ProcessWire-Clean"?? Not sure of the best way to do this but one approach might be to just maintain a fork of the main PW repo with all these changes applied. If Ryan were to link to it from the main site then folks would have the option of getting PW+demo site or the clean install.
Steve ☧
#3
MarcC
-
- Members
-
- 253 posts
-
60
Sr. Member
- LocationCalifornia
Posted 11 April 2012 - 06:50 PM
Can we also get one that comes with my next client project all set up? Thanks. 
I'm a freelance, processwire-using web designer based in california. work site | personal site | visuals
#4
alanfluff
-
- Members
-
- 405 posts
-
118
Sr. Member
- LocationOttawa, Canada
#5
Nico Knoll
-
- Members
-
- 641 posts
-
233
The Boss.
- LocationBerlin, Germany
Posted 20 December 2012 - 11:09 AM
I get this error if I'm trying to login:
This request was aborted because it appears to be forged.
This request was aborted because it appears to be forged.
#6
Soma
-
- Moderators
-
- 3,187 posts
-
1744
Hero Member
- LocationSH, Switzerland
Posted 20 December 2012 - 01:06 PM
Hasnt this to do with the salt in config.php?
@somartist | modules created | support me, flattr my work flattr.com
#7
MatthewSchenker
-
- Members
-
- 354 posts
-
211
Sr. Member
- LocationNew England, USA
Posted 20 December 2012 - 04:06 PM
I get this error if I'm trying to login:
This request was aborted because it appears to be forged.
I always get the same error. Everything installs fine and looks fine, until I try to log in.
Thanks,
Matthew
Schenker Studio (Converting this to ProcessWire right now)
27" iMac || Espresso || FileZilla || Fireworks || LibreOffice || Firefox/Firebug || Intuos5 Tablet || InkScape || ArtRage
27" iMac || Espresso || FileZilla || Fireworks || LibreOffice || Firefox/Firebug || Intuos5 Tablet || InkScape || ArtRage
#8
Soma
-
- Moderators
-
- 3,187 posts
-
1744
Hero Member
- LocationSH, Switzerland
Posted 20 December 2012 - 05:01 PM
Hmm ok, seem to sorted it out. PW doesn't create a /site/assets/sessions folder. Once I create it manually it works.
Have no idea currently what's about it, something that's different in new versions? Ryan?
Have no idea currently what's about it, something that's different in new versions? Ryan?
@somartist | modules created | support me, flattr my work flattr.com
#9
Soma
-
- Moderators
-
- 3,187 posts
-
1744
Hero Member
- LocationSH, Switzerland
Posted 20 December 2012 - 05:20 PM
Ok I just created a new export with latest PW core and now it seems to work better and assets folders get created again. It's now there, let me know if any issues arrive.
@somartist | modules created | support me, flattr my work flattr.com
#10
MatthewSchenker
-
- Members
-
- 354 posts
-
211
Sr. Member
- LocationNew England, USA
Posted 23 December 2012 - 10:46 AM
Hi Soma,
Thank you for the update. I'll go in and try this again.
Having a "blank" starting point is definitely a great option.
Thanks again,
Matthew
Thank you for the update. I'll go in and try this again.
Having a "blank" starting point is definitely a great option.
Thanks again,
Matthew
Schenker Studio (Converting this to ProcessWire right now)
27" iMac || Espresso || FileZilla || Fireworks || LibreOffice || Firefox/Firebug || Intuos5 Tablet || InkScape || ArtRage
27" iMac || Espresso || FileZilla || Fireworks || LibreOffice || Firefox/Firebug || Intuos5 Tablet || InkScape || ArtRage
#12
Nico Knoll
-
- Members
-
- 641 posts
-
233
The Boss.
- LocationBerlin, Germany
Posted 12 January 2013 - 12:51 PM
Still get the same error...
I gave ALL files 777 before I continued the installation but assets only contains "index.php" and "installed.php"...
#13
Soma
-
- Moderators
-
- 3,187 posts
-
1744
Hero Member
- LocationSH, Switzerland
Posted 12 January 2013 - 01:13 PM
I don't know, anybody else got same issue? It's working fine.
@somartist | modules created | support me, flattr my work flattr.com
#14
Martijn Geerts
-
- Members
-
- 373 posts
-
168
Sr. Member
Posted 12 January 2013 - 03:03 PM
Still get the same error...I gave ALL files 777 before I continued the installation but assets only contains "index.php" and "installed.php"...
I had the same issue with 2.2.12 . I removed the installed.php, installed it again & then run the sql again that was in the profile. After that problems solved. ( was not blank profile but my own delegate-profile ( will test again & want to simplify the profile )
#15
Wanze
-
- Members
-
- 341 posts
-
365
Sr. Member
- LocationBern, Switzerland
Posted 26 January 2013 - 07:28 AM
Hi Soma,
Just used your profile and I had the same Issue with the error message after the login. Turned out my sessions folder was missing too, so I created it manually with Permissions chmod777 and it worked.
What I observed:
Normally when installing Pw with the default profile, I have to give my assets folder + site/config.php write access. In my case, this is 777.
With your profile, this was not the case. But the permissions on the assets folder were 755, so maybe that's why the sessions folder doesn't get created.
Weird... 
Cheers
#16
Soma
-
- Moderators
-
- 3,187 posts
-
1744
Hero Member
- LocationSH, Switzerland
Posted 29 January 2013 - 04:51 AM
It seems all profiles that are exported and installed this way suffer from this problem. You have to create the folders manually. I already created a new profile using the latest PW and the issue remains. Maybe Ryan knows more about and how it could be fixed. So it's not a problem of this profile but the Profile Exporter and how it all works.
So I can't really do anything to fix it. It's not possible to give permissions to folders that are in the repository.
@somartist | modules created | support me, flattr my work flattr.com
#17
ryan
-
- Administrators
-
- 5,771 posts
-
3114
Hero Member
- LocationAtlanta, GA
Posted 29 January 2013 - 09:44 AM
I was able to duplicate it here with the blank profile, but not other profiles. I tracked it down to the lack of a /site/install/files/ directory. It looks like the installer needs there to be a files directory present for some reason (something I think I can fix). And of course, this being a blank profile, it has no files. But to get this profile working today, all you need to do is make sure you have a 'files' dir in /site/install/. There doesn't have to be anything in it.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
