benbyf

Thanks! @thomasaull

1. I mean on the settings page the is a link to a log, which when clicked takes you to the logs overview page with an error saying the log you were trying to access doesnt exist.
2. disabling auth doesnt create an open endpoint as you still need an apikey to access anything without an error
3. sounds good but how do you implement this as there is nothing in the docs?
4. ?
5. cool beans, but my comment still stands ?

Sorry for all the questions ... Its not clear to me currently how version numbers or api keys or users are related and can be used to auth against a certain route... is that something we have to build into the api call to test the signed in user and their restrictions? be cool if this was tired into the auth stage/routes as you have all the parts there available but not tied together for some reason...?

Also, anyway to create a no apikey GET endpoint. could make this using templates but be nice it it was part of the same system

Hi @Sebi I saw that form_version associated with an aplication apikey doesnt get checked at all on request, is it worth adding it, when filled, to the routes... e.g. when blank route to /api/test when 1 route to /api/v1/test ?

HELLO! Some reason the log wasn't created for this module, wondered if this was something anyone had a view on or needed fixed. I'm running PW 3.0.148

HA! you do know what i mean then!!! ? well I'll shut up then.

I guess in that case its solving the big content VS config divided present in all CMS's. But yes, i am cyrptic it seems. I guess my point was if I dont need the auto upgrading and downgrading that the module provides then I could not use it and simply write some template and field php code that you can cool as a "migration" as your module is a wrapper for quickly doing those tasks (exlcuding the uping and downing).

In an ideal world the changes would be recorded in situ (no need to write them) and migrations would be exported to file to added to version control that can be ingested by any other PW install running the module. (I'm just all about writing less)

Am I right in saying that this module is less about migrations and more about automation? As using methods to do work using handy functions in a linear way sounds like automation to me, where as migration is something I want to do when I have a bunch of stuff that has happened to the environment that needs replication for some reason (i.e exporting and importing fomr staging to live).

I only mention it as ideally you would work on your PW install (in the admin or in code) and at certain points take a migration of the changes... and therefore not need to hand write the migrations at all, as they're actaully artifacts of changes to the db?

Bit meta, but I like using the admin, and would rather migrations were something that happened, not that needed writing. (this is coming from some experience with a migrations module in Drupal 6... yes i know! That did just as explained)

Running PW 3.0.165 and have added to config.php:

$config->moduleInstall('directory', true);
$config->moduleInstall('download', true);
$config->moduleInstall('upload', true);

but with no change in the admin... stil unable to update modules, or grab them via urls ? whats the deal here?

Thanks @B3ta -  I feel like yours comments are somewhat off topic from this module specifically, so keen to get your feedback there if you have any. 
however, I do concur you thoughts on premium market place and there is actually a couple, one of which I started building myself then got busy and never got finished. It would be easier if we could all just use one central place, and easier for new PW users.

@B3ta possibly. what where you thinking?

I’m mostly interested in input to help me, as it’s a bit rough Around the edges at the minute and wondered if anyone had feedback or PRs.
I’ve recently done a lot more on it on a clients version which I’m looking to roll in soon, but am looking for enthusiasm for it so it’s not wasted work.

Had this issue again recently using ProcessWire 3.0.62 on shared hosting. I managed to fixed the issue with 777 on both templates and assets folders (as didnt help just on assets for some reason..?) but I'll need to go in a take a look around the hosting as this is massively not good ? Will report back.

On 6/20/2020 at 11:21 PM, cb2004 said:

Would be nice if this was supported in the core as well in the settings tab. I setup my redirects in there now and use the 404 logger module as that seems to cater for my current needs when rebuilding a site

yeah, core redirects would make sense, something that I can imagine seems common enough and can link in with the tracking of page url changes and redirecting.

not sure I understand how you're doing it, can you explain?

ProcessRedirects doesn't seem to support forwarding wo url with queries, this possible to enable?

e.g. my forwarded url is added as /page/?somevar=1 but the forwarded url goes to /page/

Totally worked thanks @adrian, I guess I just don't expect things to go this bizarrely wrong. After updating I found my template with the same name as the repeater. I added the template again and now everything is fine...

4 hours ago, flydev ?? said:

You already know that you might have to backup and upgrade your site to the new master. Since this version (3.0.62) there have been a number of various fix including repeater. 

will give it a go, thanks.

Hello, and welcome to what I though was either my client being silly and changing things, or some evil doer. Turns out its reproducible and therefore something in Proceswire (I checked my templates and modules but couldnt find anything that would be doing this...). So what is it doing? Check out the video for evidence.

A repeater field is interacting with a page template and another repeater field somehow to swap the fields in the template and repeater over...

I have a template called team, and a repeater field called team_repeater with label Team. Some how and for some reason, when I change my fields on repeater called main_menu_links my team template gets those fields and when I try and revert the team template fields to the fields it should have, they get given to the repeater main_menu_links. Also this to say HELP!!!!!

video: https://www.dropbox.com/s/exkdhc6n7x0xpsa/strange-repeater-PW-mega-bug.mov?dl=0

Seem to be getting strange behaviour on the input field where when a date is selected e.g. 21st. After save, the input reflects the 20th instead...? Any one had this?

PW3.0.62, datetime 1.0.6

Anyone done much with plans/products/subscriptions? going round in circles abit. looking to create a customer, add and plan/subscription, and charge them for the first installment, but cant seem to work out the API flow to put it all together ?

10 hours ago, Rob(AU) said:

Hi Ben, I've been using another Payments module. Am I understanding correctly that yours does not depend on the PaymentModule?

If not I can uninstall the unused modules ...

 

Thanks

It does, but doesnt really need to. it uses the PaymentModule for inhereitance of structure. As my module doesn't totally adhere to the render structure it might be worth striping out the dependancy at some point.

1 hour ago, elabx said:

Piece of cake with ProcessWire I say ?!

Registration with LoginRegister Pro, feedback/rating with comments module and probably I'd think of an admin dashboard or someway to present comments/rating in a nicer way than just going to the video page and look at the fields. 

If you didnt want to build an admin module you could add functionality to your templates depending on the user role. e.g. Superuser can see who has watched each video on the video's page, and you could provide a page which only exists for the admin that displays a list of videos and users who have watched them etc etc

I wonder if the latest version has soved some of this as I'm also getting errors when using the spam filtering ?

GRRRRRRRR ok found something that worked in the form settings for pages two levels deep i have to turn off Disable session tracking and CSRF protection? which must be getting in the way and disallowing everything. not sure how to get around this but might add a honey pot as replace meant... but either way I get LOTS of spam before sooooooo not great... gonna have to fob off FormBuilder at this rate

so works fine on the / and /apply/ pages respectively but not the /privileges/bvlgari/

http://supercarownerscircle.nicegrp.com/

Doesn't seem to submit correctly on that page as I'm unable to see anything in the $input variable ?

Thanks, no it’s a client site but it has the same behaviour as the form is built by the form builder module not me ?