Perch V4 (and hereafter) Megathread

  • Gareth S
    • #201

    neillans

    Apologies for the confusion, when I said not a technical delay I should have worded it as not a delay in the bodily feature evolution.

    A Perch coming together for this week is currently existence arranged, equally before long as I take more than details to share I volition.

    • #202

    Will we get a fleck more than info on V4 features and improvements?

    • #203

    seoMatt Initially that'due south progress on the next total release, nevertheless given the issues raised above with PHP8, I'll be pushing for an update on the tickets submitted this calendar week, and then we can also requite an update on that.

    Gareth Due south Please provide an update on the tickets related to PHP8 for Version iii.two

    • #204

    Hi All,

    I will be planning to get a comprehensive update and feature list from the meeting this week.

    seoMatt This is even so being worked on from what I can see, I take chased it this morning and will let you know asap.

    • #205

    Well, that went well. when visiting domain.com/perch I get an HTTP 500 error after uploading the Perch Shop v1.ii.vii files :cursing:

    And update on this Glen. Is it all the same an issue?

    • #206

    Hi All,

    An update on the Feature list for V4 is below, this doesn't include the Mobile UI improvements.

    • Nighttime Mode UI: An option added in Full general Settings, night mode image attached (epitome non 100% concluding, could be subject to changes).
    • Integration of Perch Runway features into Perch, including an option under Settings > Features to enable/disable these features (for simplification).
    • Drove Indexing: If a user is starting to hit performance problems and a Collection is condign tedious, they tin can create a custom index. This involves giving it a name, and then picking the fields from the collection that you want to be able to sort and filter on (the fewer the better). In the background, nosotros then create a new database table with a copy of the data but in a traditional optimised table structure containing only the fields they desire in the index. When retrieving information to a folio, the user would specify which alphabetize they want to use (if any).
    • #207

    That sounds like uncommon user mistake.

    SKU's are widely understood as needing to be unique, it's the whole indicate. Entering "GRE" for both greenish and grey sounds like someone needs to type "what is an SKU" into Google! :-) We need less distractions towards V4, not more!

    Yep. Information technology'south user error. But in an area where a client is expected to enter information, just saying it needs to exist unique isn't really good enough. If it's a shop with a lot of products or options they're likely not going to know if it'south unique or not, specially for options.

    It would be better for the system to pick this upward and inform you that the SKU you've entered isn't unique, rather than just allowing it with no feedback and so just not working. Any other CMS I've used other than Perch will either tell you lot it's not unique or put a number on the end to go far unique. Then most clients that have used other due east-commerce solutions before aren't going to exist worried nigh if what they've entered is unique or not.

    I realise there's more than pressing bug for V4 and shop. But your response reads like this isn't worth the hassle and should simply be ignored? When it IS an consequence that needs fixing.

    • #208

    Hello All,

    An update on the Characteristic list for V4 is below, this doesn't include the Mobile UI improvements.

    • Dark Mode UI: An option added in General Settings, night manner epitome attached (image not 100% final, could be bailiwick to changes).
    • Integration of Perch Track features into Perch, including an option under Settings > Features to enable/disable these features (for simplification).
    • Drove Indexing: If a user is starting to hit performance problems and a Collection is becoming slow, they tin can create a custom index. This involves giving it a proper noun, and then picking the fields from the collection that you want to be able to sort and filter on (the fewer the improve). In the background, we so create a new database table with a copy of the data only in a traditional optimised tabular array structure containing only the fields they desire in the alphabetize. When retrieving data to a page, the user would specify which alphabetize they want to use (if any).

    I am not sure the UI update is enough for V4 - I already alter the horrible Perch UI myself with CSS. - I am not a Rail user so these updates disappoint me a lot. Seems more of a V3.5 than a V4.

    • #209

    Quote

    I am non sure the UI update is plenty for V4

    There are more than thing listed in the post including the integration of Rails features into standard Perch. It's not just a UI update as I sympathise it.

    • #210

    I know there was talk of back-ups being moved into standard Perch. Obvs, I don't know if that is part of the update, merely wouldn't this exist useful for standard Perch?

    • #211

    I know there was talk of back-ups being moved into standard Perch. Obvs, I don't know if that is part of the update, but wouldn't this exist useful for standard Perch?

    Yep this would be extremely helpful for me since I focus on Standard Perch. For a Content Management System I enjoy Perch. I don't demand a ton of characteristic creep or additional bells and whistles at the expense of ease of use. I just desperately need everything to be compatible with PHP 8 and staying compatible with PHP moving forward.

    • #212

    Hi All,

    An update on the Feature list for V4 is below, this doesn't include the Mobile UI improvements.

    • Dark Mode UI: An selection added in General Settings, dark mode image attached (image not 100% final, could be discipline to changes).
    • Integration of Perch Track features into Perch, including an option under Settings > Features to enable/disable these features (for simplification).
    • Collection Indexing: If a user is starting to hit performance problems and a Collection is becoming irksome, they tin create a custom index. This involves giving it a proper name, and then picking the fields from the collection that y'all desire to be able to sort and filter on (the fewer the better). In the groundwork, we then create a new database table with a copy of the data but in a traditional optimised tabular array structure containing simply the fields they want in the index. When retrieving data to a page, the user would specify which index they want to use (if any).

    Could y'all expand on Point 2 please? That's quite a big item - also when is the expected release engagement?

    • #213

    There are more than thing listed in the post including the integration of Runway features into standard Perch. It's not just a UI update as I understand it.

    I know more was listed but so vague I couldn't comment on those points.

    I was mainly referring to the UI update because that'southward of import to me. A dark manner being the only UI update in V4 is pathetic. Perch 4 really needs a UI overhaul with its bill of fare construction and certainly how Blocks work.

    So nosotros have gone from a test version being ready to now vague comments and screenshots which are not quite final. Perhaps it's me but information technology feels like nosotros're going backwards hither Gareth?!

    • #214

    I'k most interested and concerned virtually the release date. Specially every bit nosotros were expecting to have the a preview version by now. What's the electric current release schedule?

    • #215

    Hi All,

    Regarding the Nighttime Manner UI update, that work is done, I only said information technology's not terminal equally annihilation could change prior to total release.

    The Perch and Runway integration - this is work that was underway by Drew which has been rolled in, I have asked for more clarification, and we are waiting on a meeting with Drew to go over some items, including the release build likewise.

    I have chased all parties my side today regarding the meeting and a schedule update, however haven't anything dorsum equally yet.

    • #216

    Based on a discussion with a third political party Perch developer (who'south not on this forum), I believe there are several problems with the Store update described here Perch V4 (and future) Megathread

    Two bug that he describes:

    1. Part of the lawmaking in the perch shop gateway now depends on a "confirm" option in the payment options. I don't have this "confirm" value in my setup

    1. Find: Undefined index: confirm in /data/Workspace/some-website/public/perch/addons/apps/perch_shop/lib/gateways/PerchShopGateway_default.class.php on line 55

    2. The return_url has been changed to success_url in the payment options. and then if you're only swapping out the store app, you probably won't redirect to your confirmation folio after a successful payment

    His other comments were that:

    Quote

    Neither Perch 3.2 or perch_shop are ready for PHP eight in whatsoever mode. Tonnes of deprecation warnings which will fill your logs in no time. Unless y'all're willing to go through them and right them I would expect and keep my fingers crossed that the Perch squad are going to fix it. In terms of a developer it'due south really not hard or that bad to correct

    ----


    I promise these issues can be reported dorsum and fixed.

    • #217

    Hi Clive Walker

    Thank you, and thank you to your colleague - I'll study this to our development team now then they can look into these items, I will update you on the Store app as soon as I hear dorsum from them.

    • #218

    Any news on your meeting with Drew?

    • #219

    Any news on PHP 8 compatability with Perch three?

    • #220

    Hi All,

    Our lead developer, Theodora is having a technical coming together with Drew on Tuesday. In the mean fourth dimension, Clive Walker in regards to the comments from the developer yous discussed with, I accept been asked to get more details on this, namely effectually PHP8. When our evolution team have tested this they loaded the update on PHP8 server and weren't given given any errors/warnings.