Regarding a problem when checking “Upload Image”
-
Thank you for your continued support. I appreciate this wonderful version update.
Currently, I am testing Gwolle Guestbook 5.0.1 on my test site. For safety reasons, I haven’t yet performed full functionality testing in the production environment.
By the way, when I check “Upload Image” in the “Other” tab of the Gwolle Guestbook add-on settings, the decorative toolbar above the text box on the new post screen disappears.
Even after unchecking “Upload Image,” it doesn’t return to its original display state. How can I restore it to its original state?
Is this feature simply not available yet?
Or is there a problem with the database or settings on my test site?
The page I need help with: [log in to see the link]
-
Hi Senri,
That is strange, it should not happen.
Could you doublecheck at Guestbook > Settings > Form-tab if Visual editor is enabled?
Maybe something else went wrong when updating.Regards, Marcel
Hello Marcel,
I’m sorry, it was completely my mistake.
The settings you suggested solved the problem!
Therefore, you can mark this thread as resolved.
Thank you so much for your help despite your busy schedule.P.S. I’ve successfully completed the Japanese localization work for Gwolle Guestbook 5.0.1.
Best Regards,
SenriSubsequent testing has shown that image uploads to the guestbook are now completing successfully.
We don’t plan to support image uploads in the production environment, so it’s fine for now, but the upload message becomes invisible against a black background, so CSS changes seem necessary.
In any case, the problem is resolved. Thank you very much for your help.
-
This reply was modified 1 week, 6 days ago by
Senri Miura.
-
This reply was modified 1 week, 6 days ago by
Senri Miura.
For your reference, on my site, which has a black background, I have implemented the following CSS in conjunction with the release of Gwolle Guestbook 5.0.1.
/*
Gwolle Guestbook button design change
*/
.gwolle-gb-write-button input {
font-size: 9pt !important;
}
.gwolle-gb-write-button {
.button {
display : inline-block;
border-radius : 5%; /* rounded corners */
font-size : 9pt; /* font size */
text-align : center; /* text position */
cursor : pointer; /* cursor */
padding : 12px 12px; /* padding */
background : #000066; /* background color */
color : #ffffff; /* text color */
line-height : 1em; /* line height */
transition : .3s; /* smooth transition */
box-shadow : 0px 0px 8px #666666; /* Shadow setting */
border : 2px solid #000066; /* Border specification */
}
.button:hover {
box-shadow : none; /* Remove shadow when cursor is hovered */
color : #000066; /* Background color */
background : #ffffff; /* Text color */
}
}
/* Upload button */
.button.gwolle-gb-addon-upload-button {
background : #000066;
border-color : #666666;
color : #A0A0A0;
font-size : 10pt;
}
/* Submit button */
.button.gwolle_gb_submit {
font-size : 10pt;
}
/* Preview button */
.button.gwolle_gb_preview {
background : #000066;
border-color : #666666;
color : #A0A0A0;
font-size : 10pt;
}-
This reply was modified 1 week, 6 days ago by
Senri Miura.
-
This reply was modified 1 week, 6 days ago by
Senri Miura.
Hi Senri,
Thank you for the translation work.
Is there anything you need here? I often look at the strings like “author wrote ondateattime“. I can imagine it doesn’t work in every language. But I never dared to really touch it, because it has grown quite convoluted over the years.Glad you can make the CSS work for you.
Hello Marcel,
Thank you for your reply. I truly appreciate your ongoing support.
Please rest assured that the Japanese localization process is proceeding very smoothly.
Regarding the translation work itself, simply translating strings within GlotPress does not always yield the most appropriate results.
Therefore, although it takes more time, I’m carrying out the translation by actually running the plugin and carefully cross-referencing the text displayed on the screen with the strings in GlotPress.Japanese nuances and phrasing can be particularly challenging; however, the availability of Google’s AI translation as an aid has been a great help, allowing me to achieve higher translation accuracy than before.
Here is one example: while the word “author” might typically be translated simply as “筆者 (writer)” or “作成者 (creator),” I have standardized the term to “投稿者 (post author)” (tōkōsha) to better align with the nature of this plugin, which focuses on posts.*Translation Example
en: Show author email in Metabox.
ja: 投稿者のメールをメタボックスに表示するAdditionally, regarding the CSS for Gwolle Guestbook 5.0.2 designed for themes with dark backgrounds: changing the
border-radius: 5%;definition toborder-radius: 5px;results in a cleaner display.
I’m sharing the modified CSS below for your reference:/*
Gwolle Guestbook button design change
*/
.gwolle-gb-write-button input {
font-size: 9pt !important;
}
.gwolle-gb-write-button {
.button {
display : inline-block;
border-radius : 5px; /* rounded corners */
font-size : 9pt; /* font size */
text-align : center; /* text position */
cursor : pointer; /* cursor */
padding : 12px 12px; /* padding */
background : #000066; /* background color */
color : #ffffff; /* text color */
line-height : 1em; /* line height */
transition : .3s; /* smooth transition */
box-shadow : 0px 0px 8px #666666; /* Shadow setting */
border : 2px solid #000066; /* Border specification */
}
.button:hover {
box-shadow : none; /* Remove shadow when cursor is hovered */
color : #000066; /* Background color */
background : #ffffff; /* Text color */
}
}
/* Upload button */
.button.gwolle-gb-addon-upload-button {
background : #000066;
border-color : #666666;
color : #A0A0A0;
font-size : 10pt;
}
/* Submit button */
.button.gwolle_gb_submit {
font-size : 10pt;
}
/* Preview button */
.button.gwolle_gb_preview {
background : #000066;
border-color : #666666;
color : #A0A0A0;
font-size : 10pt;
}-
This reply was modified 1 week, 1 day ago by
Senri Miura.
P.S. About translation…
The following sentences l’lI be not translation in Japanese because the word order might be rearranged, potentially resulting in an unnatural meaning:
%1$s wrote on %2$s at %3$s
Aha, interesting. Can you tell me more?
Currently translations are quite fixed in their order. It’s really ‘author from Japan wrote on day at time’. When I always understood that many languages can have a really different order.
You could now for example make it into:
%2$s at %3$s, %1$s wroteWould it make more sense if it were just two headings, one for the ‘name from origin’, and a separate one for ‘date at time’?
Regards, Marcel
Assuming the settings %1$s = Author, %2$s = Year, and %3$s = Time:
In English, it is:
%1$s wrote on %2$s at %3$s
In Japanese, the word order becomes:
"%1$s は %3$s の %3$s に投稿した"
The meanings of the individual words are as follows:
'に' (ni): at
'の' (no): on
'投稿した' (toukou shita): wrote
Simplified, this becomes:
"%1$s は %3$s %3$s に投稿"
However, since translating "wrote on" simply as "is" is inappropriate, the conclusion is that the parameters for "%1$s wrote on %2$s at %3$s" should not be translated.
Next, let us examine the following parameters:
%2$s at %3$s, %1$s wrote
This expression deviates even further from standard Japanese phrasing, so it likewise cannot be translated directly.
Incidentally, translation becomes relatively easy with parameters like the following:
Post Date: %2$s at %3$s by %1$s
Japanese translation: "投稿日時: 2026年6月30日 @ 12:30 by Name"
English translation: "Post Date: June 30, 2026 at 12:30 by Name"Hi Senri, thank you for the response.
Maybe the one sentence is simply too complicated 🙂
I cahnged it again in git and svn. Now there is only:
Name from City
Date at Time
Both on their own line. I think is most languages this is more straightforward when translating.
Does it help?Hello Marcel,
Yes, I think so.
That way, it’s simple and shouldn’t cause any issues for translation.Thank you, that is good to hear.
-
This reply was modified 1 week, 6 days ago by
You must be logged in to reply to this topic.