Jump to content

Kaseem

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

17 Good

About Kaseem

  • Rank
    Jr. Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So you don't see the login page at all? Maybe the browser gets confused because the IP address you use was used for another site earlier. Can you try to clear the browser cache and cookies from the site?
  2. I assume you are referring to a call of the following format: http://10.0.71.8:8105/processwire/page/ This is the call to my testing site. Works like a charm for me, both in the front and back end. Do you just use a standard installation?
  3. Sorry, my answer above was probably not very helpful. I am actually not sure if I understand your question or reasoning. You refer to two different options How do the two options render in your browser? <link rel="stylesheet" type="text/css" href="/site/templates/assets/uikit/css/uikit.min.css" /> - does not work? <link rel="stylesheet" type="text/css" href="/site/templates/assets/css/uikit.min.css" /> - works? So probably if the following does not work http://mysite.com/site/templates/assets/uikit/css/uikit.min.css Does the following link then work? http://mysite.com/site/templates/assets/css/uikit.min.css Just wondering if the uikit.min.css is rather located in the folder /site/templates/assets/css/ and the folder /site/templates/assets/uikit does not actually exist? According to my understanding of PW, the default settings in the .htaccess file only direct requests to php and other system files to PW root index.php whereas files like .css or .js are handled by the web server directly. Maybe someone more knowledgeable can answer this question.
  4. Hi @neophron, Just some thoughts to find the cause of this behaviour. Do you have full control over the PW installation? Does the folder ../templates/assets and all the files within have the same ownership and rights as the containing folder (or any other folder)? I ask because this is not a standard folder and it was created specially at some point. Also, you might want to check your .htaccess file in the site root folder. Is there a rule which prevents the access? Hope this helps for a start.
  5. I am compiling this list and the contributions of @szabesz - thanks a lot. To make contributions to the documentation based on the code, it seems best to contribute to the code on https://github.com/processwire/processwire and send a pull request to @ryan To make contributions to the rest of the documentation, it seems best to send them to @ryan for example by pm. PW Documentation API Reference : Gives an overview of the API variables and detailed information about the class functionality. This is directly generated from the source code (see API Explorer module) based on a special markup code included in the PHP comments. Tutorials : As the name suggests, giving insights into a number of topics. API Cheatsheet : A comprehensive reference of ProcessWire API variables, methods and properties – all on one page. The intention is to pull this information also directly from the code using the API Explorer module (see this post - What about the cheatsheet - is this actually implemented by now?) API Documentation : Learn more about the API including the concepts behind it, how to work with template files, and how to develop modules. Also labeled as: DEVELOPING A SITE IN PROCESSWIRE. Covers additionally topics like Concept, Template Files, Selectors, Include&Bootstrap, Syntax, Hooks, Plugin Modules, Users&Access, Arrays, Fieldtypes, Multi-Language Support and Coding Style Guide. Directory Structure : This section outlines ProcessWire’s default directory structure, highlighting the locations where your site’s files go. Template Files : Every time a page is loaded on your site, ProcessWire looks at what template is assigned to the page, loads it, gives it several API variables, and then runs it as a PHP script. This section covers the use of template files and serves as an introduction to using ProcessWire’s API with examples. This can be accessed also by way of "API Documentation" Selectors : A selector allows you to specify fields for finding a page or group of pages that match your criteria. Selectors in ProcessWire are loosely based around the idea and syntax of attribute selectors in jQuery. This can be accessed also by way of "API Documentation" Multi-Language Support : ProcessWire makes multi-language support easy with multi-language fields, URLs (page names) and code internationalization. Security : Security is our number one priority with ProcessWire. Make it your number one priority too. In this section we attempt to cover some of the more important aspects in maintaining a secure installation. Install & Upgrade : Covers installation of ProcessWire, troubleshooting and upgrades. More on how different ways how documentation is generated or updated in these posts: https://processwire.com/blog/posts/processwire-3.x-api-reference/ https://processwire.com/blog/posts/processwire-3.0.16-continues-expanding-documentation-and-more/ https://processwire.com/blog/posts/processwire-3.0.41-and-a-look-at-api-explorer/
  6. Thanks @Doug G for your offer. I see myself a bit in the same situation. Maybe it is helpful to summarise here the documentation as it is available on the PW website and then ask for contributions to this list as to get a full picture of what already exists and what is actually still missing. PW Documentation API Reference : Gives an overview of the API variables and detailed information about the class functionality. According to @horst 's post this is directly generated from the code based on a special markup code included in the PHP comments. Tutorials : As the name suggests, giving insights into a number of topics. How to contribute to the tutorial? API Cheatsheet : A comprehensive reference of ProcessWire API variables, methods and properties – all on one page. Is this also directly generated from the code? API Documentation : Learn more about the API including the concepts behind it, how to work with template files, and how to develop modules. Also labeled as: DEVELOPING A SITE IN PROCESSWIRE. Covers additionally topics like Concept, Template Files, Selectors, Include&Bootstrap, Syntax, Hooks, Plugin Modules, Users&Access, Arrays, Fieldtypes, Multi-Language Support and Coding Style Guide. How to contribute to this documentation? Directory Structure : This section outlines ProcessWire’s default directory structure, highlighting the locations where your site’s files go. Template Files : Every time a page is loaded on your site, ProcessWire looks at what template is assigned to the page, loads it, gives it several API variables, and then runs it as a PHP script. This section covers the use of template files and serves as an introduction to using ProcessWire’s API with examples. This can be accessed also by way of "API Documentation" Selectors : A selector allows you to specify fields for finding a page or group of pages that match your criteria. Selectors in ProcessWire are loosely based around the idea and syntax of attribute selectors in jQuery. This can be accessed also by way of "API Documentation" Multi-Language Support : ProcessWire makes multi-language support easy with multi-language fields, URLs (page names) and code internationalization. Security : Security is our number one priority with ProcessWire. Make it your number one priority too. In this section we attempt to cover some of the more important aspects in maintaining a secure installation. Install & Upgrade : Covers installation of ProcessWire, troubleshooting and upgrades. Is there more documentation hidden on this site? Or on different sites?
  7. Thank you @kongondo for this very useful tutorial. The version when find() was added seems to be 3.0.66. I have now created a pull request with the version info of when the functions find() and includeOnce() were added using the @since syntax suggested by @Robin S
  8. Following up on @Robin S suggestion, I have thumbed up the suggestion regarding the @since to the syntax used for the generation of documentation. I guess technically I can go ahead and suggest a corresponding change to the PW git repository and once @ryan gets around it he can include it if he thinks it is helpful. Would anyone help me with another question flowing from the above? How can I find the PW version in the file history on github? I have found the change when the function "find" was added to "wire/core/WireFileTools.php" https://github.com/processwire/processwire/commit/786995f85e3664615fe2cc5ff269f4bd59b6a7f2#diff-fd4a44895145a0f0ea6d437d7e7b62c0 Where can I find the PW version under which this commit was later released?
  9. Thanks to everyone for the very helpful comments and links @horst and @Robin S. The difficulty I see as a newbie is not so much how ProcessWire is working as it is a very straight forward architecture and well documented with examples. My challenge has been to find my way around the forums and the documentation. So far I hesitated asking questions because I don't want to sound too ignorant and overstretch the hospitality of this community. I appreciate all your help very much and I will see how I can really contribute in the future as I think that PW does deserve wider recognition.
  10. I have been using ProcessWire for a while now and I really like to work with it. I am not a big developer but I much appreciate the way it is setup and how the community is supporting it. Recently I was trying to update a template file and I realised that the function "find" in the core "WireFileTools.php" class was only added rather recently (July 2017) to the 3.1 version of PW. So I have some questions that maybe someone can try to answer for me: - is the online documentation in https://processwire.com/api/ref/ intended to reflect only the most recent develop branch or should it include references to additions and changes done to the 3.x? In this case that the function was added only in version 3.x. - maybe an easier question, how is the API Reference documentation created? Is there a way to contribute on GitHub? Thanks for your help Kaseem
  11. Today I made the update for VersionControl from version 1.2.7 to version 1.2.8 using the ProcessWireUpgrade module. My test site runs PW core version 3.0.52. After the update the site was producing the following error which I found in the error log file: Compile Error: Cannot redeclare class VersionControl (line 18 of /home/chr/ac-test-pw/site/assets/cache/FileCompiler/site/modules/PageSnapshot/VersionControl.module) I noticed that there are now two folders containing the file "VersionControl.module": "VersionControl" and "PageSnapshot" After removing the folder "PageSnapshot" with the old version of "VersionControl.module", everything seems to work properly again. It actually appears that installing the module using "Modules > New > Add module from URL ..." will install it in the folder /site/modules/PageSnapshot where as the "ProcessWire Upgrade" module will create a new folder /site/modules/VersionControl which is the recommended folder for the installation of the module according to the module page http://modules.processwire.com/modules/version-control/
×
×
  • Create New...