Recently Browsing 0 members
No registered users viewing this page.
I'm trying to figure out what might be the best approach when using PW for your CMS, but needing access custom tables. I know you can query your custom tables, so that's not my question here. What I'm trying to figure out is if I should separate an application from PW.
Out of the box, the application I will be using has its' own tables and the app is built towards using those tables, so I don't want to rewrite the app to use PW, seems too much work.
I do however want to use PW for the CMS and frontend where my users can add/update rows in those custom tables. Now the app itself can be connected from various devices on a handful of ports, so I'm expecting a high volume of requests to the app to a point where I'm seriously considering a dedicated server for this project.
Would it be beneficial to create a whole subdomain just for the app and use PW to query the db? Or should I keep the 2 in the same db? Pros/Cons would be great here.
By Kiwi Chris
More than a year after I submitted a proposal, I finally was given the contract to build a new website for a regional promotion organisation, promoting a very sparsely populated part of NZ.
The original website I think was running CMS Made Simple, however it was not mobile friendly, and the organisation of directory listings into categories was unreliable, and edits required requests to the original developer.
My brief was to make the site mobile friendly, and user editable, although I also ended up providing some of the photography as some of the site owners were slow to come forward with material themselves. I didn't rewrite content as that was beyond the scope of what I was asked to provide.
Bootstrap 4 came out after I'd already started the project, so it's built using Bootstrap 3.
Modules I used:
Admin Restrict Branch (So owners of listings can log in and edit their own listings, but nothing more) AIOM+ - I found the LESS compilation handy, as I could work with the Bootstrap source files and adjust variables rather than overriding compiled bootstrap. Fieldtype Phone - so I could easily format phone numbers so that they would work both as URLs and display correctly. Social Share Buttons - although I created a modified colour set of icons. Jumplinks - to map URLs from old site to maintain SEO.
Upon reading these articles
I was thinking that PW can be used for a Jamstack or Headless CMS with no changes at all.
You can easily create REST Api with PW or use the GraphQL module
So ProcessWire is an Open Source Headless CMS since 2010
I'm building a site and i noticed that loading time is very slow when we enter the site address for the first time. It takes about 1 minute or more just to start loading files and displaying the content.
However, after that period it's very fast and everything is ok. Once the page(s) is/are loaded, i can refresh them quickly and without any delay.
any one faced like this problem? and what can i do to resolve it.
hosted type: VPS
this message appear in admin dashboard: " Warning: your server locale is undefined and may cause issues. Please add this to /site/config.php file (adjust “en_US.UTF-8” as needed): setlocale(LC_ALL,'en_US.UTF-8');"
The site: http://almanassah.net
I have my own register-login-profile/account page system. I know that Ryan recently released an official module for this, but there may be an advantage to having my own custom solution. Anyway, it seems to work well.
But, I have been getting annoying Russian hack attempt accounts, mostly as 'guests' that don't bother to use the activation link.
Most if not all of these accounts have this in the name field:
No Subscription Detected
...which makes them relatively easy to filter out from real name accounts.
Where do these "strings" come from? I can't find them in Processwire's source. Are the hackers using some kind of tool that inserts these for some reason? Or is it a PHP thing? Does anyone recognize them? Does it mean they are using some kind of backdoor instead of the registration form?
In general, what are the best practices to secure my registration form, prevent spam accounts, etc.?
I'll start with adding a check to block IP addresses that try to register with 'Not Recognized' etc. in the name field I guess.