Thread Rating:
  • 3 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
GetSimple Blog
Actually, I was thinking it was as you and mr_clarke have both described. It caused by a php error that occurs after the backend has outputted, but before the plugin finishes outputting, hence why you see the php error when you enable debug mode.

The php error you have quoted above unfortunately doesn’t give me enough information about where the problem is occurring. If possible, please try installing the x-debug extension to your php instance, then report back here with the stack trace that x-debug will output.

X-debug and installation instructions can be found here: xdebug.org

Note: debug mode needs to be enabled for x-debug to work.
Check out my website: JohnStray.id.au
Reply
(2017-11-30, 01:45:56)johnstray2001 Wrote: Actually, I was thinking it was as you and mr_clarke have both described. It caused by a php error that occurs after the backend has outputted, but before the plugin finishes outputting, hence why you see the php error when you enable debug mode.

The php error you have quoted above unfortunately doesn’t give me enough information about where the problem is occurring. If possible, please try installing the x-debug extension to your php instance, then report back here with the stack trace that x-debug will output.

X-debug and installation instructions can be found here: xdebug.org

Note: debug mode needs to be enabled for x-debug to work.

oh - i see... Blush 
this is the stack of xdebugger – hope this tells you more than it does to me…:
[Image: xdebug.png]
Reply
since i am running another website with a working gs-blog plugin, i tried to mirror the working website on the website with the dysfunctional blog plugin – and this one worked. the working gs-blog version was 3.5, so i changed the blog version on the dysfunctional website from 3.4.3 to 3.5.
at a first glance this combination of getsimple and gs-blog seems to work. since x-debug shows some alerts, i want to make them accessible here:
[Image: xdebug-gsblog5.png]

[Image: xdebug-gsblog5-frontend.png]
Reply
I see you have abstained a copy of the latest beta 3.5.0. Those php warnings that you have posted there are because sitemap.class.php is not finished yet, it’s currently a work in progress.

You can either follow the github issue #48 and wait until I’ve finished it, or as a temporary workaround, remove the calls to the new class inside /gs-blog/class/Blog.php. You’ll find the calls in saveSettings(), savePost() and deletePost().


The last php error is related to github issue #104. I look into a fix for that.
Check out my website: JohnStray.id.au
Reply
hi,
i installed dynpages successfully - i use it on a blog page for blog posts of one certain category (as described in this forum on page 1 for user xxdex). it worked for about 30 minutes, then suddenly the page is showing all blog posts with all categories and xdebug is throwing the following errors:
[Image: xdebug-dynpages-category-page.png]
i am not sure if the errors are caused by dynpages or gs-blog. can you give me a hint on what the problem might be?
Reply
You can test it on a normal page to see if it works there.
Reply
(2017-12-06, 20:48:45)datiswous Wrote: You can test it on a normal page to see if it works there.

thanks – but also normal pages show the xdebug-errors and don't show only the selected category posts. insted, all posts -– no matter what category – are displayed. Sad
Reply
Looks like there's some error in your component code. Like a $workshop variable that has not been initialized...
Reply
(2017-12-07, 02:22:03)Carlos Wrote: Looks like there's some error in your component code. Like a $workshop variable that has not been initialized...

the funny thing is: it worked at first. then after some minutes and out of the blue (i had not edited anything in the plugin settings, scripts,...) the errors came up and the posts were shown no matter what category.
what could i do? reinstall the plugin and all its referring data xml files?
Reply
(2017-11-24, 01:31:14)johnstray2001 Wrote: @pigsound: I'm not sure if I can help with this. I can't seem to find anything that could be causing the issues your having. If anyone else has any ideas, please feel free to make some suggestions...

Hi John, I'm having the same problem (I think). The DATE_DISPLAY in /gs-blog/lang/en_US.php is set to '%B %e, %Y' - this formatting only seems to apply to the main blog, not when using show_blog_recent_posts. This is what I see in recent posts: 2017-11-26 10:28:34. I've read every comment on this forum at least a half-dozen times but don't see a solution. Any idea what I'm doing wrong? 

UPDATE: A few other issues I've had since originally writing this post - wondering if you can provide any insight... Sorry for all of the questions but the support website doesn't seem to have any information.

1) i18n Search - the posts aren't showing up in search results, is there a way to fix that?
2) No meta data for posts:
  • page description
  • page title (won't work with "Custom Title" plugin either)
  • og:image for social media sharing
3) Links added using ckeditor in posts don't support hierarchical URLs, I see "https://www.domain.com/%parents%/slug/" instead of "https://www.domain.com/parent-slug/slug/"
4) Recent Post date formatting mentioned above
5) Posts aren't included in sitemap.xml
Reply
In a new installation, gs-blog.php shows in the list on the Plugin page and it can be activated. Once done, clicking on  the Blog tab causes the plugin to deactivate (crash?) and the Blog tab disappears.

Required directories are writable.


Snooze
Reply
In debug mode this message is received:

Warning: call_user_func_array() expects parameter 1 to be a valid callback, function '' not found or invalid function name in /srv/disk4/2175727/www/lexluthor.eu5.net/admin/load.php on line 39
Reply
Latest version in Extend (listed as 3.4.3, though the plugin says 3.4.2) doesn't work with PHP 5.3 - crashes the site until you remove it.
With debug mode:
Code:
Parse error: syntax error, unexpected '[' in [...]plugins\gs-blog.php on line 19
Reply
(2018-04-20, 07:27:56)snoozeburg Wrote: In debug mode this message is received:

Warning: call_user_func_array() expects parameter 1 to be a valid callback, function '' not found or invalid function name in /srv/disk4/2175727/www/lexluthor.eu5.net/admin/load.php on line 39

Anything on this behavior? Same happens with a MAMP installation.
Reply
Hi,
Blog is working fine, but there is a problem I can't solve.
I create few categories. When blog shows all categories there are 8 posts on a page, but if I choose one category, all of posts are shown. But in some category I have 100 posts. How can I set tne number of post shown in particular category. 
Thanks.
Reply
Hello everybody,
I have a strange problem with this plugin. If I copy it into the required directory and then enable it in the Plugins tab everything seems OK at first glance. But it disables any other plugin which reload of the Plugins tab testifies - one other plugin is disabled. The disabled plugin cannot be enabled then till the GetSimple Blog plugin is disabled again.
I checked the file /data/other/plugins.xml and found this: every installed plugin gets its record in this file (between <item></item> tags); but if I install and enable the plugin GetSimple Blog the first record in the file is replaced by <item><plugin><![CDATA[user-managment.php]]></plugin><enabled><![CDATA[false]]></enabled></item> (with the misspelling quoted) - this way the plugin the record of which was in the first place here is disabled in user administration and cannot be enabled again (its record is no longer present in the file). The misspelling user-managment.php leads me to the file /plugins/gs-blog/inc/common.php where it says

PHP Code:
if($phpfiles[0] !== 'user-managment.php') { # Only reorder if user-managment is not first
 
   if(($key array_search('user-managment.php'$phpfiles)) !== false) {
 
     unset($phpfiles[$key]);
 
   }
 
   $temp = array('user-managment.php');
 
   $phpfiles $temp $phpfiles;
...


and so on but I cannot manage it further (I don't understand purpose of the condition) so I must ask for help.
The plugin is of most recent version (3.4.3) by the way.
Reply
@bensayers: I'm not sure what you mean with that... The function show_blog_recent_posts() doesn't output any date...
1. I may have to do some more extensive testing with the i18n_search plugin. I'm not too sure why they are not showing up in results.
2. Better metadata management is in the works for the next version (3.5.0). Follow GitHub Issue #104
3. I've never encountered this one before either. I will check this out and see what I can find.
5. SiteMap inclusion is a new feature in 3.5.0. Follow GitHub Issue #48

@snoozeburg: I need more information to be able to figure that php warning out. Please install xdebug and send me the stack trace.

@Carlos: Use php 5.4 or later. If for whatever reason you do need to use 5.3, you could try this workaround (not tested):
PHP Code:
# Change the following from:
Line 19define('BLOGLANGUAGE'$languageValues[0]);

# To:
Line 19$bloglang $languageValues[0];
Line 20define('BLOGLANGUAGE'$bloglang);

# Alternate Option (if above still doesnt work):
Line 19define('BLOGLANGUAGE''en-US'); 

@lotova: This has already been fixed in the next version (3.5.0 beta). Refer GitHub Issue #116. Download the GitHub Repo and install the blog from there.
Check out my website: JohnStray.id.au
Reply
Brick 
Version 3.4.4 is now available on Extend
This version includes the following changes:

This is an interim bugfix release just to address the few known bugs that currently exist from the previous version, allowing for successful use of the plugin until such time the next major release becomes available.

Bug Fixes:
  • [#109] Fixed class constructor after previous rewrite. Fixes the message 'Blog Settings Successfully Saved!' Message always being displayed.
  • [#115] Fixed alignment of input field boxes in the metadata section of the post editor.
  • [#117] Hide tags when there are no tags attached to a post.
  • [#119] Removed some unused variable declarations.
  • [#122] Fixed incorrect double slash in GSBlog->listPosts function.
  • [#125] Unpublished posts (dated in the future) could not be viewed when accessed directly for previewing.
  • [#131] Fixed trailing comma showing at the end of the list of tags.
  • [#132] Fixed PHP parse errors for improper method of accessing array element.
  • [#133] Fixed CKEditor triggered twice on Post Editor page.
  • [#135] Fixed Incorrect values used in html input/label tag attributes, causing the `blogurl` setting not to save.
  • [#138] Fixed PHP fatal error: Using string offset as an array in customFields.php

Back End (Admin) Changes:
  • [#128] Created a more uniform method of displaying success/error messages that prevents displaying on the frontend.
  • [#116] Dropped support for old UserManagement plugin

WARNING: This release drops support for the Multi User plugin, because it's too old, appears to have been abandoned, and has too many bugs to be compatible. If you are actively using that plugin in combination with this plugin, all permissions relating to GSBlog will no longer apply and all users will have full control. If you'd like to update but retain support for Multi User, please review commit 692f7ea and revert those changes (This will not be supported).
Check out my website: JohnStray.id.au
Reply




Users browsing this thread: 2 Guest(s)