Migration J3 To J4: Error > Failed Opening Required - Question | JoomShaper
Black Friday sale is live with flat 50% OFF. Sale ends soon! Grab your deal now!

Migration J3 To J4: Error > Failed Opening Required

P

Pat

SP Page Builder 2 years ago

Hi

I did migrate Joomla 3.x to J4.

In Options of SP Page Builder I did activate "SP Page Builder next". Then I did update to 5.0.9.

But update did not work. I get an error: Failed opening required '/home/mydirectory/sub.domain.dd/components/com_sppagebuilder/builder/classes/base.php' (include_path='.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php')

Joomla 4.3.4 PHP 8.1

How can I solve this?

Thanks.

0
5 Answers
Paul Frankowski
Paul Frankowski
Accepted Answer
Senior Staff 2 years ago #128643

Hi Pat,

it looks that was problem with folder permissions and component files were not uploaded/updated correctly.

The only way to fix it - is thru FTP

  1. Download SPPB Pro 5.0.9 package (com_sppagebuilder_pro_v5.0.9.zip)
  2. Unzip
  3. Using FTP upload all folders & files from /admin/ inside that folder: administrator\components\com_sppagebuilder
  4. Then do this same with /site/ - but this time here: components\com_sppagebuilder

yes, override all files inside (!)

then try to install SPPB 5 again in normal way.

0
P
Pat
Accepted Answer
2 years ago #128646

Hi Paul

Thanks a lot. I did so and now I'm a step further. :)

However, install still was not working. I got: JInstaller: :Install: SQL-Fehler Duplicate column name 'is_favorite'

Then I did a DB repair and installed the package again. This time it worked.

0
Paul Frankowski
Paul Frankowski
Accepted Answer
Senior Staff 2 years ago #128647

Ok, I think I solved the problem ... I used my File Manager component and above steps

0
P
Pat
Accepted Answer
2 years ago #128651

OK, great

But design in frontend is not correct. Please compare to live website and scroll down. I did clear cache. Still not correct (pictures too large, text too narrow).

Thanks.

0
P
Pat
Accepted Answer
2 years ago #128660

Fixed by changing some CSS.

All solved now. :)

0