Jump to content

PAGEGRID Pagebuilder: Beta Test Support


jploch
 Share

Recommended Posts

  • 2 weeks later...
  • jploch changed the title to PAGEGRID Pagebuilder: Beta Test Support

Hey @jploch looking forward to checking out your hard work. Thank you for sending over the download.

I've just created an empty DB and uploaded the packaged, unzipped it then kept the profile zipped. I get the attached error however when trying to run the setup. Any thoughts?

Screenshot 2022-10-01 at 18.00.20.png

Link to comment
Share on other sites

@alexm Sorry for that! Not sure what is causing this. Can you please redownload the files and try again (in your gumroad mail click "View content" and than the button "View content" on the product). Also make sure to unzip the folder first and than upload the content to the location were you want to install the profile. The profile already comes with the wire folder included so no need to include ProcessWire yourself.  

Link to comment
Share on other sites

Hi @jploch

I have the following JS error in the console.
 

Failed to load resource: the server responded with a status of 404 (Not Found) fieldsettings.css

Uncaught Error: [HMR] Hot Module Replacement is disabled.
    at Object.<anonymous> (main.js:1:273800)
    at Object.<anonymous> (main.js:1:273857)
    at i (main.js:1:110)
    at Object.<anonymous> (main.js:1:220711)
    at Object.<anonymous> (main.js:1:220891)
    at i (main.js:1:110)
    at Object.<anonymous> (main.js:1:273910)
    at i (main.js:1:110)
    at main.js:1:902
    at main.js:1:912

And I see a lot of this error:

Failed to load resource: the server responded with a status of 500 (Internal Server Error) __webpack_hmr

Any reason why I saw all this error?

Gideon

P.S. I am using version 0,4 and install in a sub-folder.

 

 

 

Link to comment
Share on other sites

Hi @Gideon So

Thanks! This will be fixed in the next version, you can ignore them for now, these errors should not break anything.  

2 hours ago, Gideon So said:
Failed to load resource: the server responded with a status of 404 (Not Found) fieldsettings.css

This file is not needed anymore, I will remove the call for the next version.
The rest of the errors are webpack related. I must have used the wrong build command, so should be an easy fix..

Link to comment
Share on other sites

  • 5 weeks later...
On 10/1/2022 at 8:02 PM, alexm said:

Hey @jploch looking forward to checking out your hard work. Thank you for sending over the download.

I've just created an empty DB and uploaded the packaged, unzipped it then kept the profile zipped. I get the attached error however when trying to run the setup. Any thoughts?

Screenshot 2022-10-01 at 18.00.20.png

Some as this problem with installation:

SQLSTATE[HY000]: General error: 1273 Unknown collation: 'utf8mb4_0900_ai_ci'

Created DB - utf8_bin

Server version: 5.5.62 - MySQL Community Server (GPL)

Database client version: libmysql - mysqlnd 7.4.30

Here was this collision, I think:

CREATE TABLE `textformatter_video_embed` (
  `video_id` varchar(128) NOT NULL,
  `embed_code` varchar(1024) NOT NULL DEFAULT '',
  `created` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `data` text,
  PRIMARY KEY (`video_id`),
  KEY `created` (`created`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;

in file - install.sql

Link to comment
Share on other sites

I was able to install without errors. With the configuration utf8 MyISAM

When a delete COLLATE=utf8mb4_0900_ai_ci

Other way with configuration utf8mb4 MyISAM - gives an error:

A SQLSTATE[42000]: Syntax error or access violation: 1115 Unknown character set: 'utf8mb4mb3'

My version MySQL 5.5.62

Link to comment
Share on other sites

Discovered another bizarre situation.
If you upload a video in webm format, the video is uploaded to the editor, but it is not saved.

This does not happen with the mp4 video format. The mp4 format is saved and displayed in the frontend. 

Link to comment
Share on other sites

@Andy Thanks for reporting back!

I just pushed an update (0.8) which should fix the issue with the file uploader. The file uploader now respect the extensions setting of the corresponding file field and shows an allert for unsupported file types. By default the video file field that comes with the profile (pg_video) only allows the extension mp4 (See screenshot). But you can add webm here if you want.

1028994732_Bildschirmfoto2022-11-08um12_12_02.thumb.png.4b3e2adcf11437ade9b426cfa010627b.png

  • Like 1
Link to comment
Share on other sites

On 11/5/2022 at 1:56 PM, Andy said:

I was able to install without errors. With the configuration utf8 MyISAM

When a delete COLLATE=utf8mb4_0900_ai_ci

Other way with configuration utf8mb4 MyISAM - gives an error:

A SQLSTATE[42000]: Syntax error or access violation: 1115 Unknown character set: 'utf8mb4mb3'

My version MySQL 5.5.62

I can replicate the install error with the configuration "utf8mb4". Using "utf8" with either "MyISAM" or "InnoDB" works for me.
Deleting the line "COLLATE=utf8mb4_0900_ai_ci" in install.sql is not working for me. I will have to investigate further. For now please use "utf8" instead of  "utf8mb4".

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...