Page creation errors when ProBlog Installed

Permalink Browser Info Environment
Whenever anyone tries to create a page when this addon is installed they get this 500 server error. Additionally, even site administrators with page creation permission cannot view the add/edit or settings sub pages for ProBlog on the dashboard.



{"error":{"type":"Whoops\\Exception\\ErrorException","message":"Concrete\\Core\\Page\\Type\\Type::canPublishPageTypeBeneathPage(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "Concrete\\Package\\Problog\\src\\Page\\Type\\PublishTarget\\Configuration\\BlogSectionConfiguration" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition ","file":"\/var\/www\/html\/concrete\/src\/Page\/Type\/Type.php","line":846,"trace":[{"file":"\/var\/www\/html\/concrete\/src\/Page\/Type\/Type.php","line":846,"function":null,"class":null,"args":[]}]},"errors":["Concrete\\Core\\Page\\Type\\Type::canPublishPageTypeBeneathPage(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "Concrete\\Package\\Problog\\src\\Page\\Type\\PublishTarget\\Configuration\\BlogSectionConfiguration" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition "]}

Type: Pre-Sale
Status: In Progress
View Replies:
RadiantWeb replied on at Permalink Reply
RadiantWeb
Hi there,

This is an auto responder to let you know that your support ticket has been forwarded to our entire support team at RadiantWeb!

Support tickets are reviewed Mondays thru Fridays 9am to 9pm & Saturdays 9am to 12pm EST.

A support team member will be following up with you as soon as possible.

Thank for supporting RadiantWeb Products!

RadiantWeb Support
http://goradiantweb.com
RadiantWeb replied on at Permalink Reply
RadiantWeb
uhhh..... I have no idea here. I am not able to reproduce this. All of this (5.7 core code) is so new and changing constantly...I may have to pull in the core team on this. We have seen a few file naming issues regarding various server conditions? Could be that???

Can you try to simply rename /packages/problog/src/Page/Type/PublishTarget/Configuration/BlogSectionConfiguration.php & ../Type/BlogSectionType.php to blog_section_configuration.php & blog_section_type.php respectively?

ChadStrat
Carahsoft replied on at Permalink Reply
Doing this before installing yeilds the error

Class \Concrete\Package\Problog\Src\Page\Type\PublishTarget\Type\BlogSectionType does not exist
Carahsoft replied on at Permalink Reply
And afterwards doesn't fix the error.

Just let me know if there's other information you need about our environment as well, I left a message on the voicemail for you guys if you need information that I can't just post here.
Carahsoft replied on at Permalink Reply
So I think we just managed to solve the issue. All of the folders inside of the problog root folder were uppercase, and changing those ALL to lowercase names allowed it to work. We're running this on a linux server so case sensitivity screwed us over.
RadiantWeb replied on at Permalink Reply
RadiantWeb
try updating to ProBlog v1.0.5

ChadStrat
RadiantWeb replied on at Permalink Reply
RadiantWeb
sorry....v2.0.6

C
webok replied on at Permalink Reply
webok
Hi, We've also encountered this problem.

The possible fix suggested by Carahsoft of renaming all the folders to lowercase has not worked for us.

We are running Concrete 5.7.3.1 and the latest version of the extension from the marketplace which is reported to be version 2.0.4 by the 'Add Functionality' page in our concrete install.

You mention 2.0.6 and the marketplace says that's the latest however its only given me 2.0.4

Was any other progress made on this problem?

- Greg
visuellekultur replied on at Permalink Reply
visuellekultur
Hi,
we got the same Problem when adding sites an ProBlog is installed:

PHP Fatal error: Concrete\Core\Page\Type\Type::canPublishPageTypeBeneathPage(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "Concrete\Package\Problog\src\Page\Type\PublishTarget\Configuration\BlogSectionConfiguration" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition in concrete/src/Page/Type/Type.php on line 993

concrete5 Version 5.7.3.1
ProBlog Version 2.0.4 (newest version installed on 19.01.2015, marketplace says there should be a version 2.0.6 ?)

any updates
visuellekultur replied on at Permalink Reply
visuellekultur
Hi Chad,

i just tried to install the Version 2.1.0, we have unistalled the 2.0.4 an few day before, because it broke the core functionality as described before.

Now it seems the Installation is not working correct.
1. Excellent! Your theme has a right_sidebar!
2. Install:
An exception occurred while executing 'select cID from Pages where cParentID in () and cInheritPermissionsFromCID = ': SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') and cInheritPermissionsFromCID =' at line 1


beneeth the error the Pre Install Checker say "Excellent! Your theme has a right_sidebar!" and the Install Button is still there.

But something was installed, the ProBlog section in Settings is there.
Sitemap shows a Blogsearch, but no Blog.

Ok so i added the blog_section attribute to a normal site and added the ProBlock List Block as well. Ok seems to work, butt there is no Category List / Tags eg.

Now i'm not sure if this is because we unistalled the old version, or because an error in the installer, or because something else.

What should we do now to get this working?

Best regards
Ingo
visuellekultur replied on at Permalink Reply
visuellekultur
Hi Chad,
thank you for your detailed feedback ...
I've just tested v.2.2.2 again and there seems to be no more error.

best regards
Ingo
Carahsoft replied on at Permalink Reply
Formal Refund Request: Please grant me a refund for the license assigned to this support request.
Carahsoft replied on at Permalink Reply
We've had a number of issues with this product, and it's clear to us at this point that it just needs more development time before it's worth using problog, at least on 5.7
RadiantWeb replied on at Permalink Reply
RadiantWeb
we have release several updates the last few days. Are you sure you're on the latest version??? v2.1.0?

ChadStrat
RadiantWeb replied on at Permalink Reply
RadiantWeb
it's worth mentioning, that the core updates effect addons. So when we release something, it does not get released unless it passes droves of testing. But then every new Core update earlier on that gets released, especially for larger apps, can effect functionality. We try to get that updated as fast as possible, but I was out most of last week.

But, please know, trying to develop for C5 major releases is a bit like trying to hit a moving target. And they don't really tell us what all they change. So sometimes...it's as much of a frustration for us as it is you. Because we end up looking like a failure when in reality it was working fine a week ago. lol

Just thought I would explain that. It's not that we are bad at code...its that they keep changing the code our code relies on.

It should be leveling out here this month though.

ChadStrat
Carahsoft replied on at Permalink Reply
I can appreciate the hardships involved with creating addons for a product in motion, but at the end of the day the product just did not work as it needed to. We had multiple issues which constantly caused us to lose progress, broke core site functionality, or just didn't ever work. Our refund request stands, sorry.
ntisithoj replied on at Permalink Reply
ntisithoj
i (temporarily?) got rid of the error by simply hardcoding

require '/site/root/web/packages/problog/src/page/type/publish_target/configuration/blog_section_configuration.php';

at the top of application/bootstrap/app.php

Not sure if this is going bite me in the arse at some later point, but so far, so good.

concrete5 Environment Information

# concrete5 Version
5.7.2

# concrete5 Packages
Page Selector Attribute (2.0), Social Stream (1.0).

# concrete5 Overrides
blocks/main_heading, blocks/tabs, blocks/info_box, blocks/subheading, blocks/accordion, blocks/search, blocks/image_slider, blocks/contactbox, blocks/tabs_clone, blocks/topiclisttest, blocks/vendorlist, blocks/companytype, blocks/vendorlistcontract, blocks/solve_accordion, languages/da_DK, languages/de_DE, languages/el_GR, languages/fi_FI, languages/fr_FR, languages/it_IT, languages/ja_JP, languages/nl_NL, languages/ru_RU, languages/sl_SI, languages/sv_SE, languages/tr_TR, themes/carahsoft

# concrete5 Cache Settings
Block Cache - Off
Overrides Cache - On
Full Page Caching - Off
Full Page Cache Lifetime - Every 6 hours (default setting).

# Server Software
Apache/2.4.6 (Red Hat) OpenSSL/1.0.1e-fips mod_fcgid/2.3.9 PHP/5.5.6

# Server API
apache2handler

# PHP Version
5.5.6

# PHP Extensions
apache2handler, bz2, calendar, Core, ctype, curl, date, dom, ereg, exif, fileinfo, filter, ftp, gd, gettext, hash, iconv, json, libxml, mbstring, mhash, mysql, mysqli, mysqlnd, openssl, pcre, PDO, pdo_mysql, pdo_sqlite, Phar, posix, Reflection, session, shmop, SimpleXML, sockets, SPL, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tokenizer, wddx, xml, xmlreader, xmlwriter, xsl, Zend OPcache, zip, zlib.

# PHP Settings
max_execution_time - 30
log_errors_max_len - 1024
max_file_uploads - 20
max_input_nesting_level - 64
max_input_time - 60
max_input_vars - 1000
memory_limit - 128M
post_max_size - 8M
sql.safe_mode - Off
upload_max_filesize - 2M
mysql.max_links - Unlimited
mysql.max_persistent - Unlimited
mysqli.max_links - Unlimited
mysqli.max_persistent - Unlimited
pcre.backtrack_limit - 1000000
pcre.recursion_limit - 100000
session.cache_limiter - <i>no value</i>
session.gc_maxlifetime - 1440
opcache.max_accelerated_files - 4000
opcache.max_file_size - 0
opcache.max_wasted_percentage - 5

Browser User-Agent String

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0

Hide Post Content

This will replace the post content with the message: "Content has been removed by an Administrator"

Hide Content

Request Refund

You may not request a refund that is not currently owned by you.