Jump to content

rick

Members
 View Profile  See their activity

  • Posts

    635

  • Joined

  • Last visited

  • Days Won

    6

 Content Type 

Everything posted by rick

  1. rick
    Welcome to the forum Claudio! I'll add to what LostKobrakai said, but on the subject of seo, since you specifically state seo on your site. The <head> section is missing many of the seo items, such as description, author, keywords, etc. Almost all of the alt and title attributes of the <h*>, <img>, and <a> elements are missing or blank. I would also recommend that you add a <noscript> section since your site does not display anything if the visitor has javascript disabled. On another note, welcome to ProcessWire. You will find a lot of good information here from a lot of knowledgeable members. Feel free to ask about anything. You'll find that this forum is pretty active.
  2. rick

    ProcessWire Day

    rick replied to Christophe's topic in Pub

    I've been celebrating *hic* by drinkin' scotch every day since *hic* I started using ProcessWire.
  3. rick
    Hi wishbone, First, you have the variable $box_count being set to zero within the loop, so it will always be reset -- it never reaches a value of 3. You should move it before the loop begins, like my original code example. The underscore is simply a means to separate the words of the variable name, since spaces are not allowed. It is only a convention that I use. You can use whatever naming convention you are comfortable with. Hope this helps.
  4. rick
    Hi wishbone, Yes, you are correct that css doesn't limit the number of items per row, but it will allow you to display however many items that will fit on each row depending upon the width of the display, if that is your intent. As far as the programming is concerned, php uses either the keyword OR or the characters || (two pipe characters) to designate this type of comparison. I personally prefer the keyword simply because it is easier for me to read, and becomes more readily apparent when there is a misspelling. And here is what your conditional statement says: If the number of boxes is less than 3 OR the number of boxes is greater than 3 then ... render the box content. ... else if the number of boxes does equal 3 then ... start an new line. Three issues with this structure: Going back to css, the DIV elements you use as a container are by default block-level elements, which means each DIV will be rendered on a new line, unless you change that behavior through css. If you want to bypass css, then I would recommend you render your content within a table. The count function returns the total number of items -- it will not change within your for-each loop. You will need to set a counter and increment that counter at each iteration in order to obtain the desired value. Since you are only concerned about the count equal to 3, you could rewrite your conditional statement like so: $box_count = 0; for each $boxes as $box { if ( $box_count == 3 ) { // start a new line $box_count = 0; } else { //render box content $box_count = $box_count + 1; } } Regarding the actual ProcessWire method of obtaining those boxes, I will leave to the more knowledgeable members.
  5. rick
    Sorry. I misunderstood its intent. You can still view a complete page list by simply clicking the Pages > Tree option. Hovering over the pop-out icon only displays defined bookmarks, if any. </pilot-error>
  6. rick
    Just curious if anyone has/had this same issue. When I select a user to edit from Access > Users list, the password field is populated with that user's password (confirmation field is blank), and the display is collapsed by default. When I make any change and then attempt to save it, I receive the Passwords Do Not Match message. When I am logged in as any user, and select Profile from the bottom of the page, the profile data is displayed with the password fields collapsed, but both the password fields are blank, and I do not get the non-matching password warning. Is there an option to have the password fields initially set to blank? Currently running 2.16.17 dev on localhost. This issue has been present in previous versions. Thanks!
  7. rick
    Howdy, I just upgraded my localhost to 2.6.17 dev to take advantage of the new bookmark feature. However, none of the menu entries are displayed for each of the page menu options (edit, find,...). This is the case with the default theme and with reno's theme. The following image reflects the current page menu display after this upgrade. Is there a config option I am missing? Thanks for y'alls help!
  8. rick
    At the very bottom of the page is a Mark Community Read link.
  9. rick
    Hi iNoize, I'm just trying to get a better understanding of what is going on here, so please don't take offence to my questions. Usually a 500 error is some mistake made in programming or configuration, such as an error in an htaccess file, and it is rarely (in my experience) an issue with a process, like uploading a file. Is your web server running IIS or apache or ?? Are there any entries in the web server logs corresponding to the approximate time the error occurs? I see the domain is webmailer, is the file upload processed as an attachment? Is the file upload in any way associated with a mail server? When you state the upload stops at 100%, is that based off the browser progress indication, or on an upload progress indicator function defined in your application? Have you increased the settings for memory use, timeout, upload file size, and retried the upload? Is it one specific file only that your user has an issue with, or does it affect every file regardless of file type or size? Is the PDF file being uploaded created by that user, or is it an existing PDF file, such as a form, that they have saved and want to upload? Since this issue is with one of your users, have them send you their IP so you can easily locate their connection data in the log files.
  10. rick
    Sorry. I tagged the post with 2.6.16 dev, but I don't see it.
  11. rick
    I received the following errors after setting a 'manager' role to edit users, then selecting the users option from the access menu. Notice: Trying to get property of non-object in /wire/modules/PagePermissions.module on line 226 Notice: Trying to get property of non-object in /wire/modules/PagePermissions.module on line 238 Fatal error: Call to a member function has() on a non-object in /wire/modules/PagePermissions.module on line 238 Error: Call to a member function has() on a non-object (line 238 of /wire/modules/PagePermissions.module) This error message was shown because site is in debug mode ($config->debug = true; in /site/config.php). Error has been logged. I was in the middle of debugging why I was getting a unresolvable redirect error with the ProcessDashboard module with any user role login except superadmin, so I uninstalled that module. I could then view the admin page with each of my user roles. The manager role is the only user role with edit user assigned. I don't have any other admin-related modules, such as ProcessAdminCustomPages, etc. installed. The apache error log only has entries like this: [Sun Sep 06 18:07:38.548640 2015] [:error] [pid 19250] [client 127.0.0.1:38679] PHP Warning: strpos() expects parameter 1 to be string, array given in /wire/modules/Process/ProcessPageLister/ProcessPageLister.module on line 1377, referer: http://localhost/admin/access/users/ The PW logs contain the same information as the error messages above. Any ideas where or what I've done incorrectly?
  12. rick
    I do think this is a great project, and there are many great ideas submitted by everyone. Based on my 'past-life' experience as a tech-writer, there are two approaches to this issue. One is from the target audience point of view, the other is from the product capability point of view. Since there are numerous entries in this topic where "I do it this way..." and "I do it that way...", let's set aside the point of view of the end user, and concentrate on the functionality. To do that, each entry should have at least the following things defined: The description of what the function does, The proper syntax for its use, The parameters defined, The return values defined, A simple example of each combination, And a link to the source code. I hate to admit it, but I really like the completeness of wordpress docs... https://codex.wordpress.org/Function_Reference/add_action It makes is very easy for any skill level to quickly obtain the necessary information to move forward. I also think it would be advantageous to use ProcessWire to present this information. Eating our own dogfood, kind of thing. I would like to participate on this team too, if I may.
  13. rick
    As a newbie suffering from information overload, as I am sure others are as well, I hereby bring forth this topic from the deep dark archives for further discussion. PW is great for creating and managing the various aspects of a site. Most, if not all of my projects require a customized admin interface. By customized, I do not mean special css or js only files. It is more the end-user-centric workflow that is often required when satisfying client requirements. To me, this means that I limit the existing admin interface to that of a qualified user, whereas the everyday workflow needs to be presented in a manner consistent with current client procedures. My confusion stems from having so many options that I don't yet know about -- I discover something new everyday. There is a wealth of information, suggestions, examples, etc., that the more experienced users have graciously provided ( and I want to thank them for their time and contribution ). These numerous references have lead me to re-factor multiple times, at a cost of time and productivity, in order to obtain the most efficient means of implementation; As ProcessWire's design itself has done. Some of my projects are web-based applications only, which are integrated with a client's existing site. It would be nice to see how to tailor an administrative interface to fit any existing corporate identity standards. I would also like to see the 'custom' aspect of such a tutorial address the proper way to implement an advanced back-end. I realize that PW allows us to do whatever we want by staying out of our way, and that was the primary 'selling-point' when I elected to use PW for development. But from this simplicity comes a confusion, or complexity, when attempting to design and implement an advanced back-end, eg., what tools are available for a specific task? For example, if you don't know that you should use a repeater in these circumstances, or a pagearray for that, or..., you are left falling back on what you know, which causes you to re-invent a wheel that PW currently has in place. I understand that it would be impossible to generate a sort-of overall task-analysis:procedural site map since we would be talking permutations. So why don't we use a common client scenario, and build upon it?
  14. rick
    Howdy all, Is there are setting which will leave the 'system fields', columns, and notifications displayed, or remain in the current state? The checkbox to display hidden system fields is reset if you navigate away from that page, and later come back. The displayed (viewable) columns (eg, in user list) is reset when you navigate away from the page and later come back. There are some notifications (in the accordion header of admin) which are removed after an elapsed time. I haven't found any reference to such a 'toggle' setting, but that doesn't mean I didn't overlook one. ...Or more.
  15. rick
    Welcome to the board mauricius. This is a great module! Thanks for your work. Can't wait to try it out. Do you plan an alpha release soon? [edit] Fast trigger finger
  16. rick
    Just a quick follow-up. There is no error in the PW htaccess file when running ubuntu 14.04 lamp stack. The error is, however, with ubuntu's tasksel installation of the lamp server. It missed some php5 items, such as apcu, gd, curl, etc., but they were later installed without issue.
  17. rick
    I know this error is caused by something simple in the htaccess file that I am overlooking, but I've been staring at it for hours with no luck. Can I get a fresh set of eyeballs on it please. This is an ssl only site. The site works with a test.php file in document root, but fails when trying to access PW's index.php. I've also read through this, https://github.com/ryancramerdesign/ProcessWire/issues/513 ################################################################################################# # START PROCESSWIRE HTACCESS DIRECTIVES # @version 2.5 # @indexVersion 250 ################################################################################################# # ----------------------------------------------------------------------------------------------- # Don't show directory indexes, but do follow symbolic links # 500 NOTE: Some cloud hosting companies don't allow +FollowSymLinks. # Uncomment +SymLinksifOwnerMatch and comment +FollowSymLinks if you have 500 errors. # If that doesn't resolve the error, then set it back to +FollowSymLinks. # ----------------------------------------------------------------------------------------------- Options -Indexes Options +FollowSymLinks # Options +SymLinksifOwnerMatch ## I changed this with no luck. # ----------------------------------------------------------------------------------------------- # Let ProcessWire handle 404s # ----------------------------------------------------------------------------------------------- ErrorDocument 404 /index.php # ----------------------------------------------------------------------------------------------- # Handle request for missing favicon.ico/robots.txt files (no ending quote for Apache 1.3) # ----------------------------------------------------------------------------------------------- <Files favicon.ico> ErrorDocument 404 "The requested file favicon.ico was not found. </Files> <Files robots.txt> ErrorDocument 404 "The requested file robots.txt was not found. </Files> # ----------------------------------------------------------------------------------------------- # Protect from XSS with Apache headers # ----------------------------------------------------------------------------------------------- <IfModule mod_headers.c> # prevent site from being loaded in an iframe on another site # you will need to remove this one if you want to allow external iframes Header always append X-Frame-Options SAMEORIGIN # to prevent cross site scripting (IE8+ proprietary) Header set X-XSS-Protection "1; mode=block" # prevent mime-based attacks via content sniffing (IE+Chrome) # Header set X-Content-Type-Options "nosniff" </IfModule> # ----------------------------------------------------------------------------------------------- # Protect ProcessWire system files (part 1A) for Apache versions older than 2.4: # APACHE 2.4+ NOTE: Comment out this section and uncomment second 1B below it. # ----------------------------------------------------------------------------------------------- #<FilesMatch "\.(inc|info|info\.json|module|sh|sql)$|^(\..*)$"> # Order allow,deny #</FilesMatch> #<Files .htaccess> # Require all denied #</Files> # ----------------------------------------------------------------------------------------------- # Protect ProcessWire system files (part 1B) for Apache versions 2.4 and newer: # APACHE 2.4+ NOTE: Uncomment this section and remove or comment out section 1A above. # ----------------------------------------------------------------------------------------------- <FilesMatch "\.(inc|info|info\.json|module|sh|sql)$|^(\..*)$"> Require all denied </FilesMatch> <Files .htaccess> Require all denied </Files> # ----------------------------------------------------------------------------------------------- # Override a few PHP settings that can't be changed at runtime (not required) # 500 NOTE: Try commenting out this entire section below if getting Apache 500 errors. # ----------------------------------------------------------------------------------------------- #<IfModule mod_php5.c> # php_flag magic_quotes_gpc off # php_flag magic_quotes_sybase off # php_flag register_globals off #</IfModule> # ----------------------------------------------------------------------------------------------- # Set default directory index files # ----------------------------------------------------------------------------------------------- DirectoryIndex index.php index.html index.htm # ----------------------------------------------------------------------------------------------- # ProcessWire requires mod_rewrite # ----------------------------------------------------------------------------------------------- <IfModule mod_rewrite.c> RewriteEngine On AddDefaultCharset UTF-8 # ----------------------------------------------------------------------------------------------- # If you only want to allow HTTPS, uncomment the RewriteCond and RewriteRule lines below. # ----------------------------------------------------------------------------------------------- RewriteCond %{HTTPS} off RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [L] # ----------------------------------------------------------------------------------------------- # Set an environment variable so the installer can detect that mod_rewrite is active. # Note that some web hosts don't support this. If you get a 500 error, you might try # commenting out this SetEnv line below. # ----------------------------------------------------------------------------------------------- <IfModule mod_env.c> # SetEnv HTTP_MOD_REWRITE On </IfModule> # ----------------------------------------------------------------------------------------------- # OPTIONAL: Set a rewrite base if rewrites aren't working properly on your server. # And if your site directory starts with a "~" you will most likely have to use this. # ----------------------------------------------------------------------------------------------- # RewriteBase / # RewriteBase /sc/ # RewriteBase /~user/ # ----------------------------------------------------------------------------------------------- # Access Restrictions: Keep web users out of dirs that begin with a period # ----------------------------------------------------------------------------------------------- RewriteRule "(^|/)\." - [F] # ----------------------------------------------------------------------------------------------- # OPTIONAL: Redirect users to the 'www.' version of the site (uncomment to enable). # For example: http://processwire.com/ would be redirected to http://www.processwire.com/ # ----------------------------------------------------------------------------------------------- # RewriteCond %{HTTP_HOST} !^www\. [NC] # RewriteRule ^ http://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301] # ----------------------------------------------------------------------------------------------- # OPTIONAL: Send URLs with non name-format characters to 404 page # Remove this section if it interferes with URLs of any other software you may be running. # ----------------------------------------------------------------------------------------------- RewriteCond %{REQUEST_URI} "[^-_.a-zA-Z0-9/~]" RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ index.php?it=/http404/ [L,QSA] # ----------------------------------------------------------------------------------------------- # Access Restrictions: Protect ProcessWire system files # ----------------------------------------------------------------------------------------------- # Allow screenshot files (for install.php only: this 1 line below may be removed after install) #RewriteCond %{REQUEST_URI} !(^|/)site-[^/]+/install/[^/]+\.(jpg|jpeg|png|gif)$ # Block access to any htaccess files RewriteCond %{REQUEST_URI} (^|/)\.htaccess$ [NC,OR] # Block access to protected assets directories RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/assets/(cache|logs|backups|sessions|config|install|tmp)($|/.*$) [OR] # Block acceess to the /site/install/ directory RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/install($|/.*$) [OR] # Block dirs in /site/assets/ dirs that start with a hyphen RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/assets.*/-.+/.* [OR] # Block access to /wire/config.php, /site/config.php, /site/config-dev.php, and /wire/index.config.php RewriteCond %{REQUEST_URI} (^|/)(wire|site|site-[^/]+)/(config|index\.config|config-dev)\.php$ [OR] # Block access to any PHP-based files in /templates-admin/ RewriteCond %{REQUEST_URI} (^|/)(wire|site|site-[^/]+)/templates-admin($|/|/.*\.(php|html?|tpl|inc))$ [OR] # Block access to any PHP or markup files in /site/templates/ RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/templates($|/|/.*\.(php|html?|tpl|inc))$ [OR] # Block access to any PHP files in /site/assets/ RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/assets($|/|/.*\.php)$ [OR] # Block access to any PHP files in core or core module directories RewriteCond %{REQUEST_URI} (^|/)wire/(core|modules)/.*\.(php|inc|tpl|module|info\.json)$ [OR] # Block access to any PHP files in /site/modules/ RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/modules/.*\.(php|inc|tpl|module|info\.json)$ [OR] # Block access to any software identifying txt files RewriteCond %{REQUEST_URI} (^|/)(COPYRIGHT|INSTALL|README|htaccess)\.(txt|md|textile)$ [OR] # Block all http access to the default/uninstalled site-default directory RewriteCond %{REQUEST_URI} (^|/)site-default/ # If any conditions above match, isssue a 403 forbidden RewriteRule ^.*$ - [F,L] # ----------------------------------------------------------------------------------------------- # Ensure that the URL follows the name-format specification required by ProcessWire # ----------------------------------------------------------------------------------------------- RewriteCond %{REQUEST_URI} "^/~?[-_.a-zA-Z0-9/]*$" # ----------------------------------------------------------------------------------------------- # If the request is for a file or directory that physically exists on the server, # then don't give control to ProcessWire, and instead load the file # ----------------------------------------------------------------------------------------------- RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME} !(favicon\.ico|robots\.txt) # ----------------------------------------------------------------------------------------------- # OPTIONAL: Prevent ProcessWire from attempting to serve images or anything in /site/assets/. # Both of these lines are optional, but can help to reduce server load. However, they # are not compatible with the $config->pagefileSecure option (if enabled) and they # may produce an Apache 404 rather than your regular 404. You may uncomment the two lines # below if you don't need to use the $config->pagefileSecure option. # ----------------------------------------------------------------------------------------------- # RewriteCond %{REQUEST_FILENAME} !\.(jpg|jpeg|gif|png|ico)$ [NC] # RewriteCond %{REQUEST_FILENAME} !(^|/)site/assets/ # ----------------------------------------------------------------------------------------------- # Pass control to ProcessWire if all the above directives allow us to this point. # For regular VirtualHosts (most installs) # ----------------------------------------------------------------------------------------------- RewriteRule ^(.*)$ index.php?it=$1 [L,QSA] # ----------------------------------------------------------------------------------------------- # 500 NOTE: If using VirtualDocumentRoot: comment out the one above and use this one instead. # ----------------------------------------------------------------------------------------------- # RewriteRule ^(.*)$ /index.php?it=$1 [L,QSA] </IfModule> ################################################################################################# # END PROCESSWIRE HTACCESS DIRECTIVES #################################################################################################
  18. rick
    One other thing. Have you upgraded from apache 2.2 to 2.4? If so, there are a ton of things that have changed. See here http://httpd.apache.org/docs/trunk/en/upgrading.html [edit] I see that you are running 2.4 Start here... <Directory /home/me/www/testes.dev/public_html/> Options Indexes FollowSymLinks MultiViews AllowOverride All Require all granted </Directory> Notice the order deny allow has gone away.
  19. rick
    This is great! I have one upcoming project in particular where this feature will be necessary. Thanks for setting this up!
  20. rick
    What is your document root set as in sites-enabled? You may need to set the basepath in your htaccess to match. /testes.dev/public_html/ Is testes spelled correctly? It is odd that an update would break a previously working configuration, but I don't know what they are updating. I have noticed an increase in updates to 14 recently, but haven't gotten any notices about security issues from various services. On an unrelated note, I would change Indexes to -Indexes to prevent listing the directory contents, especially on a production server. If I remember correctly, apache will want you to specify either + or - for each item if you specify that flag for one item. In other words, if you use "-" on one option, you need to use either "+" or "-" on all others. So that line would look like Options -Indexes +FollowSymLinks +MultiViews On another unrelated note I run ubuntu as well. How do you like 15? I'm running 14 LTS and haven't updated to 15.
  21. rick
    Nicely done!
  22. rick
    Dagnabit! Y'all have quick trigger fingers.
  23. rick
    I would also like to add to what thetuningspoon posted. The bigest problem that I have observed with develpopeing any application is where users not knowledgeable in the technology request more and more 'one-click' solutions to the tasks they wish to perform. I'm not knocking these users at all -- We all started with no understanding (and we should never forget that). I personally, however, do not think it is the correct approach to modify PW in this manner. It is a framework upon which we as developers build an application, and subsequently a simple-to-use interface. I only ever intend to expose the PW administration to any of my clients that are qualified, otherwise, I will construct an interface for them to use. As developers, our target audiences have a wide range of skills; from no skill at all, to the skill levels seen from the members of this forum (excluding myself). Although PW is presented as usuable by skill levels between this range, I think the responsibility lies with the user to learn the platform we recommend (assuming we pick the platform that best fits their capability and functional requirements). If they are unable or unwilling, then they might want to stick with - *shudder* - wordpress. Being new to ProcessWire myself, I am learning more and more about its capabilities, and my capabilities using it, as my framework of choice. Does PW fit every requirement? Of course not. But, in my humble opinion, it is the most robust and developer-friendly CMF I have found.
  24. rick
    Thanks adrian and pwired. I do have debug on, and any other option I can set to offer info while 'in dev mode' I'll check those links you posted. [edit] @adrian: I am using Ryan's procedure found here, https://processwire.com/talk/topic/107-custom-login/?p=735
  25. rick
    Non of those options made a difference. I've been working on two items, logging in with email rather than username, and per user type profiles. I've removed all the changes except for the cloned user templates and associated pages. I can now log in. It obviously has to be pilot error, so I will re-apply the changes, noting at each step where any failure might ocurr, and report back. Thanks pwired for the input.
×
×
  • Create New...