Jump to content

Search the Community

Showing results for tags 'profile'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

  1. Hello, I would like to publish a site profile. My template is ready but I would like to know how to “build” the /install folder. As I can see here, it contains a basic database profile and dummy content right? What is the procedure to do generate install.sql? Is it a plain database export?
  2. Hello, I'm using Processwire 2.4 and I need to export the profile for migrating. But the site is a little heavy and Export Module hangs in the middle creating corrupt files. How I can recreate what Export Module does? The Sql dump is generated, but not the complete install profile. Thanks
  3. Hello everyone, I'm working on a project where people can create their own pages on the site. Whenever anyone registers, a page with same name as username is created. Currently I'm having set up as follows: Home - Profiles - - somename - - someothername But what I need is people should be able to get a URL of their own such as example.com/somename Is there any way I can have example.com/profiles/somename to display example.com/somename? I suppose this has something to do with Hooks & routing but I'm no expert so I guess you guys can help. And happy new year to all of you. Thanks.
  4. How can I add fields to the user page in the PW Admin? I'd like to add a field for a user's full name. The blog profile created by Ryan uses a similar field named "Display name (first and last name)," but I can't figure out how that field is added to the page. I've combed through the forum and I can't find the answer to my question. Is this something done through the PW Admin or through a script?
  5. Hi all, I've just pushed a new fully responsive site profile to Github: Unsemantic Site Profile for Processwire 2.3 After having tried seven zillion responsive grid systems, boilerplates, frameworks etc. I finally opted for Unsemantic Grid System. Mainly because it supports IE7, is lightweight and includes Compass/SASS. I've designed the profile as a starting point for development according to my needs. This includes almost no styling, an easy-to-use solution for placeholder images and three teaser boxes on the front page. In addition, I converted the .sass files that come with Unsemantic to .scss because I like the syntax better. Glad if you give it a try and find it an improvement for your workflow. You can see a preview here. Download from Github: https://github.com/christophlieck/UnsemanticSiteProfile
  6. delegate profile Basically the home & basic-page template have the same fields. Home » home template Basic-Page » basic-page template Search » search template Widgets » widgets template » status:hidden widget-one, Left, Left widget » widget-one template widget-two, Right, Right widget » widget-two template [*]404 Page Not Found » basic page template » status:hidden [*]Admin Settings » settings template » status:hidden » no file » access:guest view pages Position left or right » settings template » status:hidden » no file » access:guest view pages Left setting template » no file Right setting template » no file [*]Trash defaults.inc The home & basic-page templates include ./include/defaults.inc on top and on the bottom ./includes/main-view.inc. The defaults.inc is the file for common defaults, scripts & variables. Also there's living for commonly used functions & the 12 column classname generate thingy. the 12 column grid On the home & basic-page pages you can check to disable the left & right widgets. If there are no left-widgets to render, then there's no use to render the column at all on the page. The content column then receives the width of the left-column. There are in total 12 columns, say the right column has a width of 3 and the left has a width of 4, then the leftover for the content column is 5. So if there are no left widgets, then the content colum is 9. Those numbers are set to their written equals or set to FALSE. $column['one'] could be FALSE or one, two, three, four, five, etc. $column['two'] could be FALSE or one, two, three, four, five, etc. $column['three'] could be FALSE or one, two, three, four, five, etc. main-view.inc The main-view.inc is the main markup file. In this file I'll check if "template-name.css" & "template-name.js" exists and the append them to the syles & scripts array before I output them with a foreach loop in the page head. This way I know that basic-page.css for example is always the last file & can overwrite previously set styles. The grid uses the same source ordering approach as the zurb foundation grid uses. For mobile it's often a pre that the content column is showed first but on desktop there's plenty space to have a left column first. Thereby I think that Google loves content higher in the source more then if that content is a latecomer. widgets The widgets are just chunks of HTML without <head>, <body> etc. So they can be rendered with the build in Processwire render() function. Nothin' special there. download delegate profile
  7. I have a client that wants the following functionality for an intranet site: The intranet must be password protected. Each employee must have their own individual username and password. There may be a total of 100 employees who would have access to the site. A small group of employees need to have full admin rights to add, modify, and delete pages, posts, and images. They must also be able to add and delete non-admin employees. Admins and non-admin employees must be able to modify their personal profile on the site. Profile information may contain name, email, password, bio, photo(s), and links to external social media sites. The login and profile pages should *not* look like the PW admin. Employee profile pages should be available to other employees. In other words, the site should support an employee directory. Employees must be able to comment on existing pages and posts on the site. (Not sure how to implement this requirement.) Images that are uploaded should be viewable in a slideshow gallery format. I've developed one site in PW so far, but nothing like the above requirements. I'm 90% confident that PW can handle these requirements, but thought I'd check with the PW community first before making a commitment to using PW. I could build the site in WordPress, but it may be more work than to build it in PW. If someone else has built a similar site, I am interested in hearing about your experience.
×
×
  • Create New...